Hi Alex, > No, this didn't move forward. I don't think it was ever actually filed in > the jira system? >
Hmm. > There are lots of ways to avoid this problem (into, transducers, etc) and > in practice I think most people don't find it to be an actual issue. > Well, we did face this issue in production some time back, and it took quite some time to figure out what was going wrong. Reading comments on the linked post on Stu's blog shows that quite a lot of other people have also been affected by it. > I have not looked closely at the proposed solution, but beyond the basic > "does it work" question, there are also a lot of questions about > performance, etc that would be need to be evaluated. > I think correctness > performance, at least in a core function that's so widely used (or maybe put a "warning: don't use in eager contexts" in the doc). Please let me know if I can help in any way. I'll run tests and some microbenchmarks on this and get back to you. Thanks, - Divyansh -- 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.
