Re: Has the (left recursive blowing) concat function been fixed?

I wrote the original patch, but now that it's been 2 years I don't really support it anymore. There are lots of ways one could build up an oversized stack with lazy seqs. Concat might be the most common, but it's only one possibility. I think it's better to have consistent behavior than to have

Clojure/conj hotel reservations

Hey all, If anyone else is registering late for conj, the website is showing rooms as sold out, but there are still a few available -- you have to call the hotel. Let them now the discount is under "Cognitect, Inc." I as of a few minutes ago there about 8 rooms still available ... See you there!

Re: Question about Clojure parallelization

Thank for all of your advices. 1. I used iota library for convenience. 2. Even though I updated Clojure hash-map by using the transient function, it was very slow. Because the final HashMap size is about 300,000,000. So I had no choice but to using mutable Java data structure, HashMap. 3. I

[ANN] Clojure 1.9.0-beta1 is now available

Changes to Clojure in Version 1.9.0-beta1 (since 1.8.0) 1 New and Improved Features 1.1 spec spec is a new core library for describing,

Re: [ANN] Clojure 1.9.0-beta1 is now available

Congrats everyone! What a major release. -- 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

Re: [clojure-rabbitmq] Are lazy queues still bound by memory limit?

Thank you! On Sunday, September 17, 2017 at 11:32:17 PM UTC-5, Michael Klishin wrote: > > The point of lazy queues is not that nothing ever is stored in memory. > It's that queues try to move messages > to disk very aggressively (default mode keeps a portion in RAM using > metrics such as