Recently in Slack, @grav asked about stack traces being printed in AssertionErrors (here). In the podcast he linked to, @puredanger discussed how tools including Cursive can interfere with the error messages produced by Clojure itself. I'm going to review the general classes of errors to ensure Cursive does something sensible with each of them.
This should include a review of the error handling in Clojure's AOT compilation, which doesn't handle all errors very well.
Testing matrix:
Clojure version: 1.8, 1.9, 1.10.1
Environment: clojure.main REPL, socket REPL, nREPL.
Method: direct typing into REPL, send form from file
Recently in Slack, @grav asked about stack traces being printed in
AssertionError
s (here). In the podcast he linked to, @puredanger discussed how tools including Cursive can interfere with the error messages produced by Clojure itself. I'm going to review the general classes of errors to ensure Cursive does something sensible with each of them.This should include a review of the error handling in Clojure's AOT compilation, which doesn't handle all errors very well.
Testing matrix:
Clojure version: 1.8, 1.9, 1.10.1 Environment: clojure.main REPL, socket REPL, nREPL. Method: direct typing into REPL, send form from file
Errors (from https://clojure.atlassian.net/browse/CLJ-2373):