3 ms·
They strike me as fairly poor, while not catastrophically so. The fact that such messages are typical doesn't make them not-poor. They're not, though, somethin
by pvg 17y ago
They strike me as fairly poor, while not catastrophically so. The fact that such messages are typical doesn't make them not-poor.
They're not, though, something constrained to Rails and I'm not sure a Rails-specific rebuttal would help all that much - the difficulty is fundamental when the language and abstractions of expression are different from and essentially unknown to the system that's actually doing the runtime error checking. Another commenter spoke of the infamous JSP stack traces. Googling 'clojure error messages' brought up a thread on this as an error message:
(ns foo.bar.baz
(use clojure.contrib.core :only seqable?))
#<CompilerException java.lang.IllegalArgumentException: Don't know how to create ISeq from: Boolean (NO_SOURCE_FILE:0)>