radix support not working about rewrite-clj

[xsc]

These are all cases that require some kind of metadata attached to the node describing its representation; so, this will be part of the rewrite.

Btw, I'm really grateful that you keep discovering these things. Thank you!

[zcaudate]

Would it be better to just have a seperate :number tag and to save the input as a string. The trade off really is how much understanding is given to the token and i think a string is the sufficient am the most flexible way to representing data. Something like 2r0000001 is equal to 2r1. This goes for the

On 06/05/2014, at 10:10, Yannick Scherer [email protected] wrote:

These are all cases that require some kind of metadata attached to the node describing its representation; so, this will be part of the rewrite.

Btw, I'm really grateful that you keep discovering these things. Thank you!

—
Reply to this email directly or view it on GitHub.

[zcaudate]

Another thing that might be an interesting feature for rewrite is to make it work with tools.analyser.

On 7 May 2014, at 15:55, Chris Zheng [email protected] wrote:

Would it be better to just have a seperate :number tag and to save the input as a string. The trade off really is how much understanding is given to the token and i think a string is the sufficient am the most flexible way to representing data. Something like 2r0000001 is equal to 2r1. This goes for the

On 06/05/2014, at 10:10, Yannick Scherer [email protected] wrote:

These are all cases that require some kind of metadata attached to the node describing its representation; so, this will be part of the rewrite.

Btw, I'm really grateful that you keep discovering these things. Thank you!

—
Reply to this email directly or view it on GitHub.

[xsc]

The latest releases store the original string in the :token node, so this should work now.

(z/tag (z/of-string "2r1001"))    ;; => :token
(z/sexpr (z/of-string "2r1001"))  ;; => 9
(z/string (z/of-string "2r1001")) ;; => "2r1001"

Artifact Coordinates

[rewrite-clj "0.4.3"]