Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2017-02-17

Channels

#clojure-spec
<
2017-02-17
>
gfredericks00:02:47

I miss the jovial bots

bronsa00:02:05

and the internet points

gfredericks00:02:21

oh yeah I had a lot of those I think

gfredericks00:02:43

should've sold'em before the market crashed

bronsa00:02:12

no point in crying over what could've been now

bronsa00:02:24

that was a terrible pun i apologize

gfredericks00:02:05

can we start threads based on thread messages

bronsa00:02:33

I've frequently complained to my coworkers about the lack of sub threads

gfredericks00:02:16

I miss trying to get the bots to talk to each other

bronsa00:02:40

was it you who came up with that brilliant double quoting thing to bypass their "security" measures?

bronsa00:02:02

i remember being very amused

gfredericks00:02:44

I don't think I ever achieved an infinite loop personally

bronsa00:02:44

I might spend the next 3 hours going over old irc logs to find the one I'm thinking about

gfredericks00:02:59

that would be fun to see; I don't recall anything like that

gfredericks00:02:32

this feels deceptively like a private conversation

hiredman00:02:07

deceptive indeed

bronsa00:02:16

somebody's gonna chime in real soo-

gfredericks00:02:02

it lists names at the top, but I doubt that includes lurkers

borkdude11:02:43

Clojure IRC still exists, right? Or is it effectively dead now

bronsa11:02:46

it exists but i don't think it's nowhere as active as it used to be

bronsa11:02:00

also i don't join it anymore so from my perspective it's dead and I'm mourning

shem13:02:44

it's there and still useful and enjoyable

Geoffrey Gaillard16:02:20

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 …

gfredericks17:02:16

did you check under the .test namespace @ggaillard

Geoffrey Gaillard17:02:07

I'm checking right now

Geoffrey Gaillard17:02:30

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 !

bnoguchi23:02:30

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)?

bnoguchi23:02:46

e.g., in the guide example, only generating events of type :event/search

Alex Miller (Clojure team)23:02:12

You can just invoke the generator for the result of invoking one of the method specs

bnoguchi23:02:41

@alexmiller You mean if mm is the multimethod, then (s/gen (mm {:the/tag tag-val})?

Alex Miller (Clojure team)23:02:19

Yeah, or just invoke the spec directly if you van

bnoguchi23:02:29

Won't that not constrain the tag to the given value?

bnoguchi23:02:02

i.e., :the/tag is open ended as keyword?, so will generate infinite sample of possibly non-matching keywords

bnoguchi23:02:09

e.g., for :event/type example in the guide, this would effectively be for :event/search: 

clojure
(s/gen (s/keys :req [:event/type :event/timestamp :search/url]))

bnoguchi23:02:25

Ah, I guess, I can pass gen overrides for [:event/type] to (s/gen spec overrides)

bnoguchi23:02:49

It would be cool if multi-spec generators supported overrides, to force a particular generated type, e.g.,: 

(s/gen :event/event {[:event/type] #(gen/return :event/search)})