Thanks Sean,
I had't realized this was the case. I was fooled by the fact that conformed
values often are the same as the unconformed value. That changed in the fdef
where the the arg is enclosed in a seq. My spec setup didn't work as is, but
the work around (s/cat :arg ::my spec) as the
The answer to your subject line question is: no, s/and applies the first
predicate and flows the conformed value (if valid) through any remaining
predicates – regardless of where it is used. There’s nothing special about its
use inside s/fdef. Per the s/and docstring (emphasis added):
sorry, I edited this a few times and bumbled the words. That last sentence
should say: I can think of different ways to do it, but I don't think any
of them are better. However I feel the example used above [...]
On Friday, August 11, 2017 at 1:06:39 PM UTC-7, scott stackelhouse wrote:
>
> I