>>49
I'm all for having various containers like list/vector/dict (with possibility of giving usage/type hints). Building everything out of
cons cells sounds naive and much too simplistic to be well-adapted to reality. My mantra is to give the computer just barely enough to optimize things on its own. I can't imagine the kind of optimizer that will turn an assoc list into an optimized vroom-vroom hash table, or a mere list into a vector.
As for the Clojure thing, uh, please tell me, exactly how do you figure that having immutable vectors and maps
by default is a good idea?