Thanks for the context.
It looks like this is actually the same as CLJ-1237, the scope of the issue
is just broader now with that commit. I left a comment there rather than
creating a new ticket.
On Friday, May 22, 2015 at 3:02:02 PM UTC-7, Ghadi Shayban wrote:
>
> This commit [1] for CLJ-
This commit [1] for CLJ-1589 changed dispatch for InternalReduce, causing a
bug similar to CLJ-1237 [2].
[1]
https://github.com/clojure/clojure/commit/1242c4878f3d4ef30535a22f6c74144637504fbe
[2] http://dev.clojure.org/jira/browse/CLJ-1237
On Friday, May 22, 2015 at 5:01:25 PM UTC-4, Jason Wolf
One of the most significant features of 1.7 are Reader Conditionals. I'm
pretty confident after all the discussion that has gone on that we have a
good design. However I haven't seen many or any libraries which have gone
through the porting process to use Reader Conditionals.
I've worked on portin
Just deployed to our staging environment and ran into an unexpected stack
overflow error. Here's a reduced test case:
user> (->> (range 1) (mapcat (fn [_] (java.util.ArrayList. (range
10 (reduce (constantly nil)))
java.lang.StackOverflowError:
RT.java:509 clojure.lang.RT.s
I just discovered it! 70 messages in this thread ;)
A tcp server (one of the examples) is nothing like the scenarios in the UI but
this type of reducing is what i was converging to, not for UI though...
Sent from my iPhone
> On May 22, 2015, at 9:24 AM, Khalid Jebbari wrote:
>
> I mentioned i
I mentioned it in the very first post of this discussion
Khalid aka DjebbZ
@Dj3bbZ
On Fri, May 22, 2015 at 5:57 PM, Marc Fawzi wrote:
> this looks like fun
>
> https://github.com/cdorrat/reduce-fsm
>
> ;)
>
> On Wed, May 20, 2015 at 7:26 AM, Marc Fawzi wrote:
>
>> Yup, well captured.
>>
>> On
this looks like fun
https://github.com/cdorrat/reduce-fsm
;)
On Wed, May 20, 2015 at 7:26 AM, Marc Fawzi wrote:
> Yup, well captured.
>
> On Wed, May 20, 2015 at 6:58 AM, Khalid Jebbari
> wrote:
>
>> You would want it if you want to inspect/debug/transmit/replay the whole
>> the state of your
We haven't shipped it to production yet, but I just verified that our full
test suite at Prismatic passes on RC1 after fixing a few tests that were
erroneously depending on hash ordering. Thanks everyone for all the hard
work on this release!
On Thursday, May 21, 2015 at 9:31:08 AM UTC-7, A
