[ANN] Automatic specs + core.typed release

Hi, The latest core.typed release has support for generating clojure.spec specs from unit tests. [org.clojure/core.typed "0.3.25"] ...; for very recent releases :repositories {"sonatype-oss-public" "https://oss.sonatype.org/content/groups/public/"} Here's an example

Re: [ANN] Automatic specs + core.typed release

Hi Eelke, I can't reproduce, did you just clone the project and run the steps? Can you post your REPL session? Thanks, Ambrose On Wed, Aug 31, 2016 at 8:33 AM, Eelke van Foeken wrote: > Hi, > > Great feature! I am trying the demo project. I am following the steps from > the first example, but

Re: [ANN] Automatic specs + core.typed release

I'm out of ideas. Can you send your `lein version` and `lein deps :tree` from the repo directory? Thanks, Ambrose On Wed, Aug 31, 2016 at 9:13 AM, Eelke van Foeken wrote: > Hi, > > Yes I did exactly that. clone the repo. lein repl and then int the repl: > > $ lein repl > Initializing core.type

Re: [ANN] Automatic specs + core.typed release

Try using cidre-nrepl "0.13.0". It might be in your ~/.lein/profiles.clj file. Thanks, Ambrose On Wed, Aug 31, 2016 at 10:16 AM, Eelke van Foeken wrote: > Hey, > > Apologies if I am wasting your time, I am just a beginner in Clojure, so I > might be overlooking some basic things. > > Hereby > >

Re: [ANN] Automatic specs + core.typed release

Glad to help! Ambrose On Wed, Aug 31, 2016 at 10:33 AM, Eelke van Foeken wrote: > That was it! > > Thank you. > > Op woensdag 31 augustus 2016 16:22:57 UTC+2 schreef Ambrose > Bonnaire-Sergeant: >> >> Try using cidre-nrepl "0.13.0". It might be in your ~/.lein/profiles.clj >> file. >> >> Thanks

Connecting to nREPL on Intel Edison (via Cider) - why so slow?

Hi, I'm having some trouble connecting from a Mac to an nREPL running on an Intel Edison. I'm using boot to launch the nREPL on the Edison; it's *very* slow to launch (~2 minutes 15 seconds), which is not too surprising since the Edison is a relatively constrained device (1 Mb RAM, Atom CPU at 50

Re: Connecting to nREPL on Intel Edison (via Cider) - why so slow?

My understanding is that, by default, CIDER loads quite a bit of middleware when it connects so that’s likely the cause of the slowdown. You can override the middleware to provide a more stripped-down experience (but you’ll lose a lot of CIDER’s functionality) – check the CIDER docs for that.

Re: Connecting to nREPL on Intel Edison (via Cider) - why so slow?

Another option is to use Clojure's built-in socket server (requires Clojure 1.8) it is really nothing more than a TCP socket attached to a normal Clojure repl, so you'll be loading no extra middleware or really anything at all that could slow it down. http://clojure.org/reference/repl_and_main#_lau

Re: Connecting to nREPL on Intel Edison (via Cider) - why so slow?

On Wed, Aug 31, 2016 at 12:39 PM, Sean Corfield wrote: > My understanding is that, by default, CIDER loads quite a bit of > middleware when it connects so that’s likely the cause of the slowdown. You > can override the middleware to provide a more stripped-down experience (but > you’ll lose a lot

Re: Connecting to nREPL on Intel Edison (via Cider) - why so slow?

On Wed, Aug 31, 2016 at 12:43 PM, Timothy Baldridge wrote: > Another option is to use Clojure's built-in socket server (requires > Clojure 1.8) it is really nothing more than a TCP socket attached to a > normal Clojure repl, so you'll be loading no extra middleware or really > anything at all tha

Re: Spec of conform of spec

So how would you conform something to nil or false? For example: (s/conform (s/conformer read-string) "nil") ? -- 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 mem

Re: Spec of conform of spec

I don't understand the question. What are you trying to do? On Wednesday, August 31, 2016 at 4:08:00 PM UTC-5, l0st3d wrote: > > So how would you conform something to nil or false? For example: > > (s/conform (s/conformer read-string) "nil") > > ? > > -- You received this message because you are

Re: Spec of conform of spec

user=> (doc s/conformer) - clojure.spec/conformer ([f] [f unf]) Macro takes a predicate function with the semantics of conform i.e. it should return either a (possibly converted) value or :clojure.spec/invalid, and returns a spec that uses it as a predicate/conformer.

Re: 0-arity of transducer in transduce

Mathias, I've never found a satisfactory answer to this question. It has been asked before. https://groups.google.com/d/msg/clojure/HK9LkmlRyjY/S0U1u2nQCQAJ https://groups.google.com/d/msg/clojure/uVKP4_0KMwQ/-oUJahvUarIJ Hoping someone with more insight will comment on this situation. Bobby

Re: 0-arity of transducer in transduce

Thanks Bobby! And apologies for being too lazy to search for these threads. On Thursday, 1 September 2016, Bobby Eickhoff wrote: > Mathias, I've never found a satisfactory answer to this question. It has > been asked before. > > https://groups.google.com/d/msg/clojure/HK9LkmlRyjY/S0U1u2nQCQAJ >