@scott.silver why do you need to call instrument again? I have forgotten how that works.

@scott.silver that's how I do it and I agree it's frustrating. @drewverlee the problem is that after you eval the buffer all your instrumentation is gone for those functions and does no fdef spec errors will be catched. Apart from having a custom "eval buffer" function which would call stest/instrument under the hood I'm not aware of any other solution. I might ask in #clojure-spec since it's not necessarily specific to cider

thanks @jumar; is it possible to define a custom “eval buffer” function?

Can you replicate this in just a bare clj repl? It’s not clear to me if CIDER is doing something bad or if just instrumentation is a bit sensitive

I don't think it's an issue with cider it's just about improving the workflow when using cider - see follow-up in #clojure-spec : https://clojurians.slack.com/archives/C1B1BB2Q3/p1592451407375900

It's how it works in any repl/tool I believe - the functions you re-evaluate aren't instrumented anymore and you need to call stest/instrument manually

I don’t use spec, so I can’t provide much input on the subject. I guess the simplest solution would be to avoid eval-buffer after the first time and just re-eval updated expressions. We can also have some eva-buffer-hook where you can trigger some additional evaluations if needed.

@jumar I define a collection of all the functions to be instrumented and pass them to the spec instrument function using a helper function. Then if I evaluate any function definitions I call the helper function and all the functions are instrumented again. If there was a post-eval hook that calls the helper function, then that could be convenient. For example https://github.com/practicalli/spec-generative-testing/blob/prime/src/practicalli/card_game_specifications.clj#L66-L83

an alternative solution, outside cider, that might be more in keeping with how the creators imagined spec would get it's main utality is you do generative testing of your application. It seems unlikely that clojure wil merge with typed clojure anytime soon so i expect there always to be a friction in doing these sorts of things. If you want to jump that fence part way you can try orchestra though.

Has anyone ever wanted to be able to use C-M-x or C-c C-f (in other words, the eval defun-at-point functions) inside a (comment ...) block? What I'd like is to keep their normal behavior (evaluating the top-level form you're currently in), but having a exception when the top-form is a comment, and evaluating the one-before-top-level form. It's probably a peculiar need.

I find instrumenting fdef specifications convenient during development, to help me if I am calling custom functions with incorrect arguments. Switching instrumentation on an off with a helper has been okay for now. I do want to look at using koacha for testing these before pushing code to a shared repo. https://github.com/jeaye/orchestra looks interesting, but want to get more comfortable with spec before adopting it.

I just noticed Cider is returning Java member docs and eldoc for unresolved symbols without a period, eg. (shift |) being interpreted as java.lang.StringBuffer/shift

Is this a recent regression? I don't recall this happening before

@thheller tells me that shadow-cljs auto-completion is broken in the repl, is there an issue for this I can follow for updates?