Feature Request: Optionally use a separate JVM for linting.

I was thinking that my problem #40 could possibly not be as much of a problem if flycheck clojure used a second jvm just for it's purposes. Things seem to work reasonably well in #40 if it weren't for the fact that eastwood corrupts my JVM. And it makes no promises that it won't. So who knows what else could happen that might not result in such an obvious failure. As obvious as it is now, it took me a few days to understand that it wasn't my code or something else.

Cider has had nice connection management working for a while. So I'm wondering how hard would it be to create a second JVM and use that for all of the code checking. It should probably be optional since some people might not want to be running two JVMs.

Obviously the load would have to happen twice. But otherwise, using cider's connections should be fairly straight forward. It seems like this could be an easy win given eastwood's experimental status for repl calls and it would also be faster since the working jvm wouldn't be waiting on the code checks.

If I can help in any way, I'm willing. I might be able to make a pull request, but I can't promise that. I've got other things breathing down my neck.

Inizia esaminando l’integrazione esistente di Flycheck/Eastwood e la corruzione della JVM descritta nell’issue #40. Esamina quindi il modo in cui Cider gestisce le connessioni e determina l’ambito necessario per rendere opzionale una seconda JVM per il controllo del codice. Il lavoro è completato quando la JVM di lavoro rimane isolata e il linting continua a funzionare quando l’opzione per la JVM separata è abilitata.

Scritto dal modello di indicizzazione a partire dal testo della issue.