On Tuesday, 17 September 2019 22:34:04 UTC+1, Daniel Dinnyes wrote:
>
> (let [x 42] :clojure.spec.alpha/invalid)
>
> That's an interesting one. It's failing the spec on the let's body, which
is just 'any?' , so this is initially surprising.
However s/valid? is implemented as, approximately, (no
This is a known issue, see
https://clojure.atlassian.net/projects/CLJ/issues/CLJ-1966
--
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
On Wednesday, 18 September 2019 20:48:39 UTC+1, David Bürgin wrote:
>
> This is a known issue, see
> https://clojure.atlassian.net/projects/CLJ/issues/CLJ-1966
>
2016!
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send ema
I usually try to organize related things in different files in the same
order to ease code reviewing, reading and writing new code. For example:
order of protocol method declarations, their definitions in records and
unit tests. And I was wondering what's the best way to order keys in maps
and
I do not know the specifics of this issue, but just because it was reported
in 2016 does not necessarily imply that the Clojure spec developers believe
it is a bug, rather than something than an unexpected corner case that some
spec users wish would behave differently.
Also, Rich Hickey and Alex M
