This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-17
Channels
- # beginners (52)
- # boot (116)
- # cider (21)
- # cljs-dev (44)
- # clojure (104)
- # clojure-dev (82)
- # clojure-greece (5)
- # clojure-japan (4)
- # clojure-nl (14)
- # clojure-russia (65)
- # clojure-serbia (3)
- # clojure-spec (38)
- # clojure-uk (9)
- # clojure-ukraine (1)
- # clojurescript (65)
- # clojurewest (1)
- # community-development (1)
- # core-logic (3)
- # cursive (5)
- # data-science (9)
- # datomic (13)
- # emacs (45)
- # euroclojure (1)
- # hoplon (2)
- # instaparse (23)
- # javascript (1)
- # jobs (2)
- # klipse (43)
- # leiningen (8)
- # lumo (25)
- # off-topic (7)
- # om (13)
- # om-next (3)
- # onyx (11)
- # pedestal (12)
- # planck (19)
- # proton (1)
- # re-frame (26)
- # reagent (26)
- # remote-jobs (13)
- # ring-swagger (23)
- # spacemacs (1)
- # untangled (3)
I miss the jovial bots
oh yeah I had a lot of those I think
should've sold'em before the market crashed
can we start threads based on thread messages
seems not
I miss trying to get the bots to talk to each other
was it you who came up with that brilliant double quoting thing to bypass their "security" measures?
I don't think I ever achieved an infinite loop personally
I might spend the next 3 hours going over old irc logs to find the one I'm thinking about
that would be fun to see; I don't recall anything like that
this feels deceptively like a private conversation
it lists names at the top, but I doubt that includes lurkers
still in regular use
Hi everybody !
I'm having a hard time with cljs.spec
(1.9.473). I want to instrument my spec-ed functions, but I can't find the
instrument
and instrument-all
macros it seems they have been removed… do they still exist somewhere ? I can't find any blogpost about it …
did you check under the .test
namespace @ggaillard
I'm checking right now
Great ! I had a caching problem with figwheel preventing me to :require cljs.spec.test. Cider was showing me an other file for some reason … Thank you @gfredericks !
Anyone here figure out how to constrain a multi-spec generator to generate maps constrained to always generate maps with only one of the tagged values (i.e., to always follow only one multimethod branch during generation)?
You can just invoke the generator for the result of invoking one of the method specs
@alexmiller You mean if mm is the multimethod, then (s/gen (mm {:the/tag tag-val})
?
Yeah, or just invoke the spec directly if you van
i.e., :the/tag
is open ended as keyword?
, so will generate infinite sample of possibly non-matching keywords