@sergeyw could I ask you to file an issue for this?
It’s not good if Eastwood craps out without really giving a good explanation.
Oh, and a free idea. having a linter as a nrepl middleware
Since nrepl has all the info about the running project, you could lint forms as they’re evaluated.
free idea for whom?
Anyone :)
I imagine eastwood already does this?
Nope
There is no Eastwood-nrepl middleware.
Squiggly-Clojure, however uses Eastwood though.
that’s interesting, so it doesn’t take advantage of living inside the same JVM process?
it seems eastwood has copied deps. did eastwood make any changes to that code geared towards linting, or is it only to prevent classpath conflicts?
it seems this answers the question: https://github.com/jonase/eastwood/tree/master/copy-deps-scripts
The copied deps are to enable Eastwood to lint projects that use arbitrary versions of those dependencies.
If a linted project happens to use exactly the same version that Eastwood does, then no need for copieddeps, but that is the exception, not the rule.
There are explicit warnings in Eastwood's README that one would have to be foolhardy to use Eastwood in a live running project (IMO, and I wrote that part of the README). https://github.com/jonase/eastwood#warnings-about-using-eastwood-in-a-repl
I mean, if you trust Eastwood that much not to introduce bugs into your compiled code, go for it, but the disclaimer is there as strongly as I know how to word it factually.