4 ms·
1.[], {}, #{} are not the innovation. 2. The innovation is that they are on the same level as lists. All the cool list stuff you can do with lists you can do wi
by nickik 16y ago
1.[], {}, #{} are not the innovation.
2. The innovation is that they are on the same level as lists. All the cool list stuff you can do with lists you can do with all of the structures and you can add more yourself if you want. That allows to write stuff really generic.
3. If you don't like them use (vec ), (map ) and so on. Only the most imported ones have syntax there are many data structures.
P.S. Do you really finish up all your parans yourself???
- Xurinos 16y ago> The innovation is that they are on the same level as lists. I have heard this point when comparing to Scheme (Racket). I did not understand how it applied to CL. I never found an issue dealing with the different datatypes (other than initially learning what API worked with what and what was the proper generic stuff to use). > P.S. Do you really finish up all your parans yourself??? Yes. I found paredit and its derivatives really annoying, particularly when dealing with strings and other entities. I am not always closing entire functions, so the autoclose feature was also useless to me. I can see how it can both help and get in the way when dealing with [] and {}. I do not have a strong objection to that noise. See below for my real objection to the {} syntax; it is less about the {} and more about the reason for using it.
- sedachv 16y agoHere is how Common Lisp developers view the question of sequence interface abstraction: http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/f2065aa0d9fa5d00/84f067175c1d33e6 http://groups.google.com/group/comp.lang.lisp/browse_thread/...? This discussion came up recently over the usage of Christophe Rhodes' generic sequence protocol extension to CL. Pascal Costanza makes a good point about the appropriateness of having an overly abstract interface tower, and I agree with him.