You are currently using a new, unsaved search.
1 2 3 Next >>
Invalid character literal message malformed in ClojureScript
Improve error message when trying to compile invalid octal literals
Interrupt of load-file generates java.lang.ThreadDeath exception
Add positional tracking to JSON reader
Warn on duplicate defalias'
Improve error messages by highlighting unmatched argument
Better error message for TFn app
Odd deprecation warning in face of correct API usage?
Function invoke errors report arity off by 1
Periods at end of analyzer warnings
Actual and expected on recur argument count mismatch
Don't warn if arithmetic operations done on ^int
Closure warns on unreachable checked array code
Warn when overwriting protocol method
Improve error messages by using pr-str instead of str when printing objects
Improve error message from cljs.reader/read-string when reading keyword with number first (e.g. :0seconds)
Provide more descriptive error message when invalid libspec detected
better error message when calling macros with arity
ns libspec error message misses :import
print a warning when :externs file paths can't be found.
"java.net.ConnectException: Connection refused" when running node repl
Missing preamble file causes unhelpful stack trace
Compiler error on :"
PersistHashMap's -conj implementation recurses infinitely if element to be conjed is not a vector.
Confusing error messages when ns compilation fails due to a missing dependency
Cannot call method 'fromArray' of undefined -- Clojurescript 0.0-2030
Produce errors when records are initialized incorrectly
Line numbers in stack trace are wrong when type hints satisfaction fails
When calling a multi method with the wrong number of arguments, the error message could be better.
CompilerException can be too large which is thrown due to macro spec error
clojure.spec.alpha/exercise-fn should emit a bettor error message when no implementation is found for a symbol
propagate metadata in doto forms
s/& explain-data :pred problem
s/keys explain-data :pred problem
s/tuple explain-data :pred problems
Spec generated exceptions/error messages are a regression in terms of the out-of-the-box experience with Clojure.
LispReader.java and EdnReader.java exception messages could be much more informative.
Error message for non integer index into vector could be improved.
Better error message when exercise-fn called on fn without :args spec
Confusing error conforming fspec with missing arg spec
Alternative s/cat options not error-reported
clojure.spec/map-of has confusing error message when input is not a map
improve error messages for `map-of` spec
Provide meaning error message when eval of function fails.
Unknown return type class throws NPE instead of useful exception
Bad type hints on a defn cause the compiler to throw a NPE
Mention cljc when require fails
Omit java exception class from CompilerException message
Display more descriptive error message when trying to use reader conditionals in a non-cljc file
vector-of throws NullPointerException if given unrecognized type