2013/3/25 Jim foo.bar <jimpil1...@gmail.com> > Moreover, consider the following scenario: > > -someone has heard about clojure's collections and wants to use them from > Java. > -he opens up his favourite IDE, imports Clojure and starts using a > persistent vector-let's call it 'v'. > -he types 'v.' and the IDE autocomplete feature immediately comes up with > suggestions. > -he immediately notices that .tail is accessible and assumes that this is > the proper way of 'updating' the vector. > -now, the persistence has disappeared completely hasn't it? >
Clojure's data structures were built to back clojure.core, not arbitrary Java programs. How often do you see implementation details such as PersistentVector#tail used in Clojure code? That is what matters. Erlang data structures are immutable but you can modify them in place from NIFs (native functions). A tiny fraction of projects do that. In Clojure, it is even less necessary because you have transients if you need mutability for local optimizations. -- MK http://github.com/michaelklishin http://twitter.com/michaelklishin -- -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
