Re: Bizzarre cond-> behavior

2017-07-21 Thread Milt Reder
Nicola, Wow, I certainly didn't expect to wake up to a patch, nice work. I think I get the underlying problem, seems like there might be other cases where this comes up. Thanks also to others who dared to drop my code into their REPLs to confirm, I am constantly impressed by the Clojure

Re: Migrating nREPL out of Clojure Contrib

2017-07-21 Thread Herwig Hochleitner
2017-07-18 14:48 GMT+02:00 Chas Emerick : > I would like to hear here (no more private mails, please! :-) from any nREPL users, contributors, etc. As much as possible, I would like not to debate/re-litigate the merits of contrib and its process here; let's focus on what steps

Re: Migrating nREPL out of Clojure Contrib

2017-07-21 Thread Phillip Lord
Alex Miller writes: > On Tuesday, July 18, 2017 at 1:03:09 PM UTC-5, Chas Emerick wrote: >> (Parenthetically, it strikes me as very strange for a project to have a >> copyright assignment to an individual that hasn't lodged any commits, at >> least insofar as the project

Re: Bizzarre cond-> behavior

2017-07-21 Thread Nicola Mometto
correct > On 21 Jul 2017, at 12:11, Peter Hull wrote: > > That was quick! So, if I understand it, the problem is not with cond->, it's > the chain of let-bindings it expands to? > Pete > > > -- > You received this message because you are subscribed to the Google >

Re: Bizzarre cond-> behavior

2017-07-21 Thread Peter Hull
That was quick! So, if I understand it, the problem is not with cond->, it's the chain of let-bindings it expands to? Pete -- 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

Re: Bizzarre cond-> behavior

2017-07-21 Thread Nicola Mometto
Ticket with patch + explanation: https://dev.clojure.org/jira/browse/CLJ-2210 > On 21 Jul 2017, at 11:06, Nicola Mometto wrote: > > I have a patch that fixes this, will open a ticket later today. > >> On 21 Jul 2017, at

Re: Bizzarre cond-> behavior

2017-07-21 Thread Nicola Mometto
I have a patch that fixes this, will open a ticket later today. > On 21 Jul 2017, at 10:07, James Reeves wrote: > > I can also confirm, tested on Clojure 1.8.0. The macro doesn't seem to take > long at all; it's the expanded code that takes a significant time to compile.

Re: Bizzarre cond-> behavior

2017-07-21 Thread James Reeves
I can also confirm, tested on Clojure 1.8.0. The macro doesn't seem to take long at all; it's the expanded code that takes a significant time to compile. On 21 July 2017 at 10:56, Peter Hull wrote: > On Friday, 21 July 2017 00:35:00 UTC+1, Milt Reder wrote: >> >> Here's a

Re: Bizzarre cond-> behavior

2017-07-21 Thread Peter Hull
On Friday, 21 July 2017 00:35:00 UTC+1, Milt Reder wrote: > > Here's a simplified example: > > I can confirm that pasting that defn into a CIDER repl does take a long time before the prompt comes back. I tried doing a "macro expand all" and it was pretty much instantaneous. The resulting