Hello,
I have a problem which is probably not in the spirit of clojure.spec as
being a library for "only" checking/generating valid values, but of
substantial practical value for my use case:
Let say I have a function for checking if a double precision number is
parsable from a string (where
Amazing!
Lot of thanks Josh! This solves everything. It is even written in the API
doc, but I missed the important piece of "(possibly converted) value"...
With best regards
Plamen
On Tuesday, October 11, 2016 at 8:49:16 PM UTC+2, Josh Tilles wrote:
>
> I think you’re looking for conformer
>
P.S. This is a question about clarification/advice, not a critique to
Clojure, as it actually works as advertised :)
On Tuesday, January 15, 2019 at 2:58:07 PM UTC+1, plamen...@gmail.com wrote:
>
> Hello all
>
> while working on a daily basis where I use Clojure's native vectors/maps I
> almost
Hello all
while working on a daily basis where I use Clojure's native vectors/maps I
almost never experience the problem and even if - it is easy fixable with
something like (into [] ...), I have the following problem with custom data
structures and ask here for clarification if my
Hello Alex
On Tuesday, January 15, 2019 at 3:19:05 PM UTC+1, Alex Miller wrote:
>
> Well first, there is a conscious split between collection and sequence
> functions. Collection functions take a collection and return the same
> collection (and take the collection first) - things like conj,
Hello Mark
the reason was that I want them to act as if they are maps and vectors for
an end user developer and let him work with all the usual Clojure functions
for these data structures, while internally they would have some different
implementation and additional functionality (for
P.S. Actually it just a coincidence that in my use case I am not concerned
with let say trees, but with "Records" in a "Table", which in contrast map
somehow nicely to IPersistentMap (where I can put a lot of additional
functionality in a transparent way) and a "Table" (where the sequence
Hello James
Yes. The (into (empty table) (comp (filter process?) (map process)) table)
was exactly what I wanted for an end user to avoid to have to write, but
just a (filter ... table), otherwise I could provide a wrapper like (defn
myfilter [pred table] (into (empty table) (comp (filter
