Re: Spec of conform of spec

2016-09-01 Thread l0st3d
I was asking how you would conform a value to a falsey value. If the interface for the function is that returning nil or false means that the input is not valid (which is what I understood from the discussion) then how can you conform to nil or false? However, on reading the docs for conformer

Re: Spec of conform of spec

2016-09-01 Thread Alex Miller
I think you may be confusing the return value of a predicate value (acting as a spec) with the return value of the function passed to conformer. In the former case a predicate function's return value is a logically truthy value and a return of nil or false indicates the value is invalid. The fu

[ANN] Manifail 0.4.0

2016-09-01 Thread platonovadim
Hello, I'm pleased to announce a release of Manifail - a failure/retry handling library built on top of Manifold . I know we have Diehard already, conveniently wrapping the Failsafe <

Re: [ANN] Manifail 0.4.0

2016-09-01 Thread lvh
Hi! > On Sep 1, 2016, at 12:03 PM, platonova...@gmail.com wrote: > > Hello, > > I'm pleased to announce a release of Manifail > - a failure/retry handling library built > on top of Manifold . > I know we have Diehard

Re: [ANN] Clojure 1.9.0-alpha11

2016-09-01 Thread Ambrose Bonnaire-Sergeant
Hi, There seems to be some issues instrumenting functions that compile to .invokePrim calls. user=> (s/fdef blah :args (s/cat :foo int?) :ret any?) user/blah user=> (defn blah [^long a]) #'user/blah user=> (st/instrument) [clojure.core/symbol user/blah] user=> (blah 1) ClassCastException clojure

Re: [ANN] Manifail 0.4.0

2016-09-01 Thread platonovadim
I did! After I wrote first few versions of Manifail though. One of the issues in Banach repo inspired me to add a `reset!` marker in addition to `abort!` - https://github.com/RackSec/banach/issues/12. I've tried expressing retry logic through streams at first too, but settled on a different ap

Re: [ANN] Clojure 1.9.0-alpha11

2016-09-01 Thread Kevin Downey
instrument is going to have issues with any calling convention outisde of the normal deref var + invoking path. http://dev.clojure.org/jira/browse/CLJ-1941 is a similar case with some discussion in the comments. On 09/01/2016 11:33 AM, Ambrose Bonnaire-Sergeant wrote: > Hi, > > There seems to be

Re: [ANN] Clojure 1.9.0-alpha11

2016-09-01 Thread Ambrose Bonnaire-Sergeant
invokePrim seems to be the most common alternative calling convention. I've worked around this myself for core.typed, basically generating a deftype with the correct primitive invoke interfaces based on the :arglists of the current var we're instrumenting. I can prepare a patch if this approach i

clojure.java.jdbc - upcoming (small) breaking change

2016-09-01 Thread Sean Corfield
Just a quick heads up that the next version of clojure.java.jdbc will be 0.7.0 (Alpha 1, probably) and will have a small breaking change – hence the jump from the planned 0.6.2 version. https://github.com/clojure/java.jdbc/blob/master/CHANGES.md The signatures of as-sql-name and quoted have cha