heh, enabling (s/instrument) on all instrumentable vars does not do wonders for my game’s performance

invaluable for finding the 7 random spots where i’d goofed when converting to namespaced keywords, though 🙂

i’m not complaining, i absolutely expected this degree of perf degradation when instrumenting like every function in this tight loop, it was just funny to go from 60fps to 0.5 😄

instrumenting only at the edges brings me back up to good perf, nice

guys, you remember me struggling with this: https://clojurians.slack.com/archives/clojure-spec/p1475364998003541

yeah!

so it turned out that my regex is bad

it does not take into account timezones

that minus sign sometimes is a plus sign

although I think it would be helpful if spec told me why exactly it couldn’t satisfy the predicate

i worked with a guy once whose most famous quote around the office was: <jlatt> dates suck <jlatt> f&@# time

i’ve had similar feelings when running into the “Couldn’t satisfy such-that predicate after 100 tries” error - i wish there was some way it could tell me how i’ve messed up

also I think test.chuck generator does not generate values with random timezones. maybe it should

i’m not sure how it could do that though

@danielstockton :args (s/cat :arg1 (s/and ::query (s/+ (s/or :db map? :coll vector?)))

Has this changed? http://clojure.org/guides/spec#_spec_ing_functions

Argh, I think I want s/cat instead of s/and actually

now i see that s/and is adding two specs

yep, thanks @minimal, somehow i was blind to that

We officially have clojure.spec-based code in production now — Clojure 1.9.0 Alpha 13 and all of our REST API search code relies on spec for validation and conformation!

@seancorfield any plan to write about it?

@jcsims I submitted a proposal to Clojure/conj about it… so if that gets accepted, I’ll have to write about it. If it doesn’t get accepted, I’ll probably still write it up for my blog, but in a very different format I expect.

Part of my concern is that core to a lot of what we’re doing with spec is something that @alexmiller said is essentially an anti-pattern (heavy use of s/conformer).

That, and we are still at times struggling mightily with how to apply spec to some situations...

well, looking forward to it either way 👍