I'd say that's a bug in s/nilable (and I wrote it, so I'll take the blame
:).
I created a ticket and a patch here:
http://dev.clojure.org/jira/browse/CLJ-2100
On Thursday, January 19, 2017 at 11:35:47 AM UTC-6,
marian.hor...@vacuumlabs.com wrote:
>
> Hi,
>
> this sequence of commands in Cloju
Hi,
this sequence of commands in Clojure 1.9.0-alpha14 suprised me:
=> (clojure.spec/def :test/name string?)
:test/name
=> (clojure.spec/form (clojure.spec/and :test/name))
(clojure.spec/and :test/name)
=> (clojure.spec/form (clojure.spec/nilable :test/name))
(clojure.spec/nilable clojure.core/
Hi Sean…
thanks a lot, indeed, this is a good hint :-).
Does not affect the stop strangeness, however.
I had a quick look into the code, namely update-system-reverse, and it
looks to me like the deps update is a no-op here as the update code in the
reduce is the same as in the is the update-sy
We have a strong focus on functional programming, and are great friends
with :clojureD, which happens on the very next day.
Come & enjoy a day of great talks!
BOB 2017
Conference
"Wh
