Easily verified -
https://github.com/arthuredelstein/clooj/blob/master/project.clj
-Gordon
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated -
I've used agents to wrap thread-unsafe mutable Java objects with a defined life
cycle, so that they could be used from multiple threads whilst respecting the
life cycle.
My particular case was server-side gRPC StreamObservers for long lived client
connections.
These are either usable, closed, o
Hi Alex,
Thank you for the work you've already put in to improving docstrings in
Clojure 1.9, I noticed a bunch of docstring Jiras land recently which is
really encouraging.
Specs certainly helps those of us who are familiar with Clojure and
clojure.spec already, and know how to use specs to g
With respect, I have searched prior conversations and have not found a
justification for why any? is in clojure.core rather than clojure.spec.
All the problems people have raised with any? are due to it be a predicate with
a very specific use-case (defining specs) but placed in a namespace where
This is fantastic! Thank you Alex
-Gordon
On Wednesday, 5 September 2018 13:24:02 UTC+1, Alex Miller wrote:
>
> New releases of spec.alpha and core.specs.alpha are not available. These
> releases make several changes to spec error printing and to the definition
> of the existing clojure.core ma
