Fork me on GitHub
#clojure-spec
<
2017-01-16
>
bbloom00:01:06

nah, i think it would only pause that level of the tree

bbloom00:01:17

like if you did (s/and a? b? unspeced c? d?)

bbloom00:01:31

then you would check a and b, then issue a warning, but not even bother with c or d

bbloom00:01:41

in theory it shouldn’t affect the context at all tho

rickmoynihan00:01:20

for checking… but for gen?

bbloom00:01:01

yeah, i think it would annihilate specs until an or higher up in the context

bbloom00:01:10

which matches my intuition for cut

bbloom00:01:21

or continuations in general

bbloom00:01:30

ie skip is “throw” and every or has a catch

rickmoynihan00:01:31

thats what I was getting at before

bbloom00:01:51

anyway - this is a neat idea that i have no time to investigate implementing 😉

bbloom00:01:55

thanks for the discussion tho!

rickmoynihan00:01:56

also wonder if it’s kinda like choose

rickmoynihan00:01:36

pretty sure it was called choose… will need to dig out my ansi common lisp

rickmoynihan00:01:20

ok just dug it out - it’s in “On Lisp - Advanced Techniques for Common Lisp"

rickmoynihan00:01:33

it’s basically just an operator in common lisp for doing this kinda thing - choose and fail

rickmoynihan00:01:25

anyway it’s not really helpful