I think all of these examples violate the usage expectations of transients (regardless of release) and you should expect to get confusing results from them.
I do not think it's worth modifying core.async go blocks to do anything special in this regard (eince go is a macro I don't think you can detect at compile time which locals are transients anyways). One possibility I've kicked around with some people is deciding at the time you create the transient whether it is allowed to cross threads (through a flag or something). When you don't need it you could then retain the existing safety check. -- 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.
