And last tough is that maybe there should be a build in support for
trees.
Trees are to maps like lists to vectors.
They have different characteristic on CRUD operations and CPU/RAM
resources.
With reader macros it would be possible to implement it by even not
bothering Rich Hickey.
Also there is another thought, that it would be nice to introduce
symbols priorities (like there are priorities for evaluation of
arithmetic notation),
so we could omit some parentheses (code would be compact like in
python or ruby). The would be back during the compile-time.
So with something like:
%(
let a (do-some-comp 2 3)
if a
(do-other-thing a)
map (fn [ d e ] ) list 1 2 3
)
It would be available for macros and during evaluation time as:
(let[ a (do-some-comp 2 3) ] (if a (do-other-thing a) (map (fn [ d
e ] ) (list 1 2 3)))
As you can see I can mix the code, to point the order of evaluation,
but for the rest the priorities resolves the order.
Note that the reader should have knowledge of lines (in its meta data
context).
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
