Recent activity in Errors

+1 vote

2 answers

Improve error messages for clojure.core/case

closed Sep 25 in Errors by alexmiller

0 votes

1 answer

case has incorrect + difficult-to-comprehend behavior matching 'quote on Clojure 1.10.0

commented Jul 26 in Errors by pbwolf

0 votes

1 answer

Calling deref on "clojure.core/*clojure-version*" yields "Unbound: #'clojure.core/*clojure-version*"

comment edited Jun 23 in Errors by Sean Corfield

+1 vote

2 answers

How to display better errors in clojure stacktraces? is this planned to be attacked on a new clojure version?

commented Jun 10 in Errors by Jochen Bedersdorfer

+1 vote

1 answer

Add additional arity to the ex-handler [core.async]

answer selected Apr 20 in Errors by Nikola Vojičić

+1 vote

1 answer

Namespace.java: addAlias exception could be more informative

commented Oct 14, 2019 in Errors by alexmiller

+2 votes

1 answer

tools.deps: Additional https repo not working

commented Sep 13, 2019 in Errors by Alex Whitt

+2 votes

1 answer

Failure on github import via deps

answer selected Sep 3, 2019 in Errors by Adrian Smith

+1 vote

1 answer

ex-str can be misleading when handling s/explain-data

commented Aug 4, 2019 in Errors by Jeremy Field

+2 votes

1 answer

How do I get a full stack trace instead of "... 12 more"?

answer selected Jul 26, 2019 in Errors by Paul Payne

0 votes

2 answers

Omit "null" Exception message from error output

answered Jun 26, 2019 in Errors by jira

0 votes

2 answers

Error message for non integer index into vector could be improved.

answered Jun 26, 2019 in Errors by jira

0 votes

11 answers

Badly formed pre/post conditions silently passed

answered Jun 26, 2019 in Errors by jira

0 votes

4 answers

Inconsistent reflection warnings when target is a literal

answered Jun 26, 2019 in Errors by jira

0 votes

1 answer

LispReader.java and EdnReader.java exception messages could be much more informative.

answered Jun 26, 2019 in Errors by jira

Also see all the questions in this category.

...