Re: varying realization of a lazy-seq of strings?

That's right. This happens is because collection classes' toString implementations currently delegate to RT.printString, which in turn is affected by the value of *print-readably*. Filed https://dev.clojure.org/jira/browse/CLJ-2248 with a fix. Cheers, Michał On 18 September 2017 at 03:08,

Re: Help ship Clojure 1.9!

I've run into a behaviour change that was actually already present in alpha20 – with the CLJ-99 patch in place, {min,max}-key now return the first argument with the minimum/maximum key, whereas previously they returned the last such argument. The new behaviour seems like the more natural one, but

Re: [core.spec] Stricter map validations?

Seems like that's the reasonable place to check it, otherwise you're forced into an ordering for your specs and cannot write recursive strict map specs. On Wednesday, October 4, 2017 at 8:59:59 AM UTC-7, Yuri Govorushchenko wrote: > > Thanks. This approach is also different from the macro

Re: [core.spec] Stricter map validations?

Thanks. This approach is also different from the macro because it will check specs existence at the validation time, not at the s/def call. On Wednesday, October 4, 2017 at 4:18:16 PM UTC+3, Moritz Ulrich wrote: > > Yuri Govorushchenko writes: > > > Thank you the pointers!

Re: Clojurecademy: Learning Clojure Made Easy

Here is the DSL documentation link if anyone interested in creating Clojure based courses: https://clojurecademy.github.io/dsl-documentation On Monday, October 2, 2017 at 6:47:55 PM UTC+2, Ertuğrul Çetin wrote: > > Hi everyone, > > I've created site called Clojurecademy which seems like

Re: [core.spec] Stricter map validations?

Yuri Govorushchenko writes: > Thank you the pointers! So far I ended up with writing a small `map` macro > which is similar to `s/keys` but checks that keys are already in the > registry: > https://gist.github.com/metametadata/5f600e20e0e9b0ce6bce146c6db429e2 Note that