Panic reports should be good #64

New Issue

scott · 2025-07-02T17:00:38Z

scott commented

2025-07-02 17:00:38 +00:00

Panic reports should be good! That means close parity with Janet-Ludus. Tracebacks are now possible, provide those. Line numbers are good, actual tokens will be harder to come by without a more substantial refactoring of parsing.

Panics should include the line number where they fail
Panics should have tracebacks that include line numbers and locations of callsites in parent stack frames
Match errors must report failing patterns for let and function-call match failures
Match errors should, if possible, report failing patterns for match forms

Panic reports should be good! That means close parity with Janet-Ludus. Tracebacks are now possible, provide those. Line numbers are good, actual tokens will be harder to come by without a more substantial refactoring of parsing. * [x] Panics should include the line number where they fail * [x] Panics should have tracebacks that include line numbers and locations of callsites in parent stack frames * [x] Match errors must report failing patterns for `let` and function-call match failures * [ ] Match errors should, if possible, report failing patterns for `match` forms

scott added the

errors

label 2025-07-02 17:00:44 +00:00

scott added this to the Core: CC2 milestone 2025-07-02 17:15:25 +00:00

scott commented

2025-07-04 20:14:28 +00:00

Where we are right now may as good as we get for CC2. Not the worst? We can live with this.

scott modified the milestone from Core: CC2 to Expanded: CC2

2025-07-04 20:18:17 +00:00

scott modified the milestone from Expanded: CC2 to Core: CC2

2025-07-06 06:05:24 +00:00

scott commented