Tensegritics / Tensegritics/ClojureDart
print full clojure exception on compiler error
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 1.6k
- Forks
- 119
- PR merge metrics
- No merged PRs in 30d
Description
it's difficult to debug macro logic without full exception, and this this is a new dialect so it wasn't obvious (to me at least!) that full exception wasn't being thrown
i ended up running local version of ClojureDart and printing exception myself
https://github.com/Tensegritics/ClojureDart/blob/595062ba49f0c6210aa7b69385b940386fab0872/clj/src/cljd/build.clj#L196-L202
I understand wanting to show prettier error messages, perhaps we can add a special debug flag? Happy to create PR after discussion
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at clj/src/cljd/build.clj lines 196-202, where compiler errors are currently formatted, and compare the displayed message with the full exception available during macro debugging. Clarify whether full exceptions should always be shown or exposed through a debug flag. Done means the agreed behavior is implemented and compiler errors provide the intended diagnostic detail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100