Why can I not say (spec/and (spec/keys :req-un [::id]) (spec/keys :req-un [::old-id]))?

How do I combine two map specs?

spec/merge?

That sounds correct.

I did not know this existed

There are some examples about a third of the way thru the Guide https://clojure.org/guides/spec

I scrolled threw this multiple times, but I did not see merge

Thank you.

(there's only three mentions of merge and it's easy to miss squished in between a couple of big code blocks)

Works like a charm 🙂

If I have something like this: (spec.test/check `my-fn)

Where should I put this so it will be run with other unitests?

Should I just put it like that into the test namespace?

You can run the result thru spec.test/summarize (I think) and you can write a deftest around that to assert that the summary shows success.

However, one thing to consider is that generative tests are not "fast" like most unit tests should be -- so you might want to think about having a separate task to run generative tests, so that your unit tests stay nice and fast.

Ok. So I have to write a deftest myself. Thats fine given how long it takes to run them.

summarize-results -- I had to go look it up.

question about tooling: since spec is intextricably linked to 1.9-alphas no tooling can exist for repl's until they are separated. To include spec otherwise would necessarily require hijacking the specified clojure version to 1.9, which would possibly violate people's expectations. Does this sound true and do I have any misconceptions?

I'm working on spec tooling in CIDER and I don't know how i could begin without hijacking the clojure version of the project that CIDER is interacting with

I'm not sure I follow your base assumption. Can tooling check for the existence of spec?

well in clojure 1.8, clojure.spec doesn't exist right?

ah so it would have to be wrapped in lots of conditional checks?

i was just wondering about

(ns nrepl-spec
   (require [clojure.spec :as s])

1. Unhandled java.io.FileNotFoundException
   Could not locate clojure/spec__init.class or clojure/spec.clj on
   classpath.

i havent tried it, but https://github.com/tonsky/clojure-future-spec

instead check for the existence of a var

the spec namespace is automatically loaded in clojure 1.9

that may change, we'll see

yeah that makes the problem worse, right?

(at least when running a clojure repl in 1.9)

I guess I don't get what the problem is

i need middleware to lookup specs to provide a spec browser

in cider

you're gonna need conditionals

but if you jack in from a clojure 1.7 project it's gonna blow up

well yeah the middleware needs to not be dumb

when they decouple spec from 1.9 i can just load spec in any clojre 1.7 > which is what cider supports

sure

but until then i can't even "talk" about it, i thought

like the require statement

(if (spec-available?)
  (do-cider-stuff)
  :pass)

a common thing is to try/catch around require

i guess that will have to be the case anyways, as I'm sure spec versions will be mismatched

thanks for the feedback ghadi

spec versions?

i'm assuming when it's released, CIDER will have clojure.spec 1.8 and someone might be using 1.4? or will it be like clojure.string or set where it's built in

i'm not really clear about that

didn't know if it's something that will be specified in the project file with a version or if it will be more baked into the language like set and string, etc

more conditionals

😆

haha hooray

there isn't a guarantee that clojure.spec will be released outside of 1.9 -- it's been mentioned before, but until you see a commit SHA, can't make assumptions

i sat next to stuart at dinner at the conj and he said that's what was holding up the release of 1.9. I was going off of that but i understand it's not official

This does bring up a interesting point in the discussion of middleware and nrepl. As long as tools insist on installing new deps into the repl there's going to be problems like this.

sorry not stuart but stu

tooling should degrade gracefully

not if i'm writing it

🙂

@tbaldridge you using cider or inf-clojure?

I use Cursive, you insensitive clod 😛

hehheh

haha

but I do wish all clojure tooling could move away from having middleware in the JVM repl

what are your reasons for that?

i can think of several, just curious

it just causes a lot of problems, for no real need. The dependencies used by middleware muck with the resolution order of your repl. Stuff like this spec discussion are due mostly to not being able to use spec in tooling because it might be used in a version of clojure that doesn't support it

and nrepl is too complex for something so simple, lol

all I needed was netcat + a tcp port...and now I have a RPC server inside my program

I guess it's half a rant against middleware and half about nrepl

I must admit, I too find it frustrating to need different dependencies in a project based on what a particular editor or other tooling needs. CIDER is great but with the “regular” stack of DEV middleware it takes ages to start an nREPL server. I’ve recently switched to Atom/ProtoREPL and that requires different libraries in play. For non-DEV work, we use the Socker Server but that’s “too light” for useful tooling (unless tooling was rewritten to assume a more neutral Clojure environment and just expected to execute “regular” Clojure over-the-wire).

(at the risk of continued a somewhat off-topic discussion!)

might be off-topic for spec but not in general - being parsimonious about dependencies is very important. gem install hairball applies to our community too