I was just reading about Docker+CRIU.
For me, the slow startup isn't much of a bother for normal operations of my
apps. They are generally long running services. But development is where I am
bothered by it the most. It can be painful to restart a repl and it's very
disruptive to my abilit
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 fir
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 have to say I find this confusing:
"First the :args is a compound spec that describes the function arguments.
This spec is invoked with the args in a list, as if they were passed to (apply
fn (arg-list)). Because the args are sequential and the args are positional
fields, they are almost alwa
Glad to see this separation.
Also I just wanted to chime in and say that I greatly appreciate the work
you've done with Spec. It's been a great help to me.
On Thursday, April 27, 2017 at 8:20:16 AM UTC-7, Alex Miller wrote:
>
> Clojure 1.9.0-alpha16 is now available.
>
> [...snip...]
>
Also
I restructured my data to make this section an optional sub-map, which I
think is actually better anyway.
On Tuesday, May 24, 2016 at 11:08:27 AM UTC-7, scott stackelhouse wrote:
>
> Ok.
>
> Thanks all who have worked on this, btw. It is incredibly timely for me
> and is alr
ay 24, 2016, at 1:45 PM, scott stackelhouse > wrote:
> >
> > I'm having a problem writing a spec for a map with some required
> keywords and some optional keywords. The caveat here is that the optional
> keywords are all or none... that is they are optional
I'm having a problem writing a spec for a map with some required keywords
and some optional keywords. The caveat here is that the optional keywords
are all or none... that is they are optional but if one is present they
must all be present.
What I tried to write was:
(s/keys :req [::a ::b ::c
;b" "c") ("d" "e" "f")]
>
> The benefit of using s/* in string-list is that if you wanted to include
> string-list inside another regex you could but with coll-of, it would
> always start a new collection:
>
> (s/conform (s/cat :nu
Could someone describe what a spec of a seq in a seq would look like? i.e.
['("a" "b" "c") '("d" "e" "f")]. I'm not quite "getting it."
--Scott
On Monday, May 23, 2016 at 7:12:29 AM UTC-7, Rich Hickey wrote:
>
> Introducing clojure.spec
>
> I'm happy to introduce today clojure.spec, a new cor
10 matches
Mail list logo
