Hi Alex, I understand any concurrent use of transients violates the usage expectations. Of course, if you treat any piece of mutable state sequentially like transients, you would not run into trouble either. My concern is purely about the safety that is taken away when transients 'are' used wrongly. All the examples would've throw exceptions before 1.7-alpha2, and they don't do so anymore.
Having a single go-block access a transient is valid. Having 2 go-blocks access the same transient is not and there is no warning. If at a certain point you want to 'scale' up from 1 go-block to 2 and don't realise it was accessing transients, you are potentially in a lot of trouble and there is nothing to warn you. FWIW, a flag on creating transients to make the dangers explicit would have my vote. It would also be in line with being explicit about ^:volatile-mutable and have the default be safe. -- 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/d/optout.
