RE: Order of preds in clojure.spec/alt

I would assume it’s a “maximal munch” strategy at play here: (spec/* string?) will only match one string in your input but (spec/* identity) will match all three elements so it “wins” as the best match. Perhaps :default (spec/* (complement string?)) will do what you need? (depending on exactly

Re: Two Senior Clojure developers based in Moscow looking for the interesting challenges and possibility for remote work

Hi Sergey, I would have definitly helped you out in this. I do have good Clojure Developer and Architect requirement but they are in Philadelphia, PA USA and I am not sure if you have a work visa. Lets us connect in future. Lets connect on my linkedin : https://www.linkedin.com/in/ripu-gupta-4a0930

Two Senior Clojure developers based in Moscow looking for the interesting challenges and possibility for remote work

Two Senior Clojure developers based in Moscow looking for the interesting challenges and possibility for remote work for the details please contact me here or on telegram @kaizenst -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this grou

Order of preds in clojure.spec/alt

Hi there, right now i am using spec to match some input data with something like this (require '[clojure.spec.alpha :as spec]) (spec/conform (spec/cat :stuff (spec/alt :strings (spec/* string?) ;:default (spec/* identity)

ANN: Promenade 0.6.0 - Elegant error handling and more for Clojure/CLJS

Hi, Promenade is a Clojure/ClojureScript library to elegantly handle errors and other oddities. The 0.6.0 release adds support for (1) wrapping functions that throw exceptions, and (2) early termination in reducing functions. URL: https://github.com/kumarshantanu/promenade Docs: https://github

Re: Calling proxy without reflection

https://dev.clojure.org/jira/browse/CLJ-2379 > On 2 Aug 2018, at 10:22, Nicola Mometto wrote: > > yes, the problem is with `proxy` and redefinition, I'm working on a patch to > fix this > >> On 2 Aug 2018, at 07:55, Mark Engelberg > > wrote: >> >> For those fo

Re: Calling proxy without reflection

yes, the problem is with `proxy` and redefinition, I'm working on a patch to fix this > On 2 Aug 2018, at 07:55, Mark Engelberg wrote: > > For those following along at home, it turned out not to be a problem with the > lein-virgil plugin. It's apparently a bug in Clojure. Renzo and I distill

Re: Calling proxy without reflection

And there's less! It's not necessary to issue the first (defn... or (get-test... (I tried in Clojure 1.8 only) -- 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 me

Re: What Happened to "java -jar clojure.jar hosehead.clj" ?

Also note that if you install clj, you have everything you need to run a repl at that point - it embeds an uberjar including tools.deps.alpha, clojure, spec, and all the transitive deps needed to run clj, so there are no further downloads required (until you start using deps, which inherently r

RE: What Happened to "java -jar clojure.jar hosehead.clj" ?

I wouldn’t rule out some sort of bundle artifact like this in the future, but the audience for this (that is not better served by installing clj) is quite small imo. That is, the audiences we are serving are something like: 1) people using Clojure for project work - need transitive dep resolut