This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-04
Channels
- # beginners (25)
- # boot (14)
- # business (1)
- # cljsrn (2)
- # clojure (180)
- # clojure-korea (14)
- # clojure-russia (8)
- # clojure-spec (9)
- # clojure-uk (17)
- # clojurescript (110)
- # cursive (14)
- # datomic (18)
- # emacs (23)
- # events (4)
- # garden (7)
- # hoplon (44)
- # lein-figwheel (1)
- # liberator (4)
- # london-clojurians (1)
- # om (10)
- # om-next (2)
- # onyx (22)
- # protorepl (60)
- # re-frame (36)
- # reagent (11)
- # ring (10)
- # yada (5)
I’m guessing this comes up a lot - the fact that conformed values flow through the validation process seems to make it difficult to compose specs. Say I’m writing some preconditions for a function, I have to look at the spec definitions to know if I’m going to get, say, raw values, or [tag value] pairs. Am I missing something?
OK just discovered s/unform. Adds some verbosity to some specs, but at least removes the dependency.
@tslocke I saw some speculation a while back that spec will eventually have two versions of s/and
; not sure if that's exactly what you were referring to
yeaaah, still not quite sure what’s causing an infinite loop or otherwise such bad perf it might as well be infinite - best i can offer at the moment is these stack traces: https://gist.github.com/brandonbloom/dfa559f81ad1b6d0980c120d86a2e18e
definitely related to the collection stuff tho b/c every makes it random, coll-of makes it every time