Fork me on GitHub
#clojure-spec
<
2017-03-14
>
cfleming00:03:59

FWIW Cursive doesn’t use any middleware at all.

cfleming00:03:21

I’m a big fan of loading the server-side code I need over the REPL connection when it’s opened.

cfleming00:03:53

But tooling like CIDER that uses the REPL more than Cursive does are very prone to this sort of problem, right.

tbaldridge00:03:23

Never thought of it that way, static analysis saves you from having to do a lot of the server side stuff.

cfleming00:03:29

I don’t think there’s a solution other than saying “this functionality won’t work unless you’re using Clojure 1.9+"

cfleming00:03:06

Generally I try to make sure that Cursive will work independently of the version of Clojure the user is using.

cfleming00:03:53

I’m actually looking at some REPL improvements right now, and if I want to use EDN then that means a Clojure 1.5+ project. Fortunately I know which version the user is using and can warn them, but it’s a little ugly.

cfleming00:03:40

@tbaldridge BTW pure socket REPLs are on the way.

cfleming00:03:44

(in Cursive)

cfleming00:03:32

But again, there I have to check that the user is using 1.8+

devth02:03:10

is there a way to grab the :ret spec out of an fdef? trying to validate the return value of a fn in a test

Alex Miller (Clojure team)03:03:59

Yep, just call get-spec on the symbol to get the function spec

Alex Miller (Clojure team)03:03:30

That spec implements ILookup and can be invoked with :ret

Alex Miller (Clojure team)03:03:06

So, (:ret (s/get-spec 'full/symbol))

devth13:03:34

excellent. thanks.