Nice error reporting

scott commented

2024-05-19 19:14:49 +00:00

Owner

Copy Link

Stand up a system of presenting errors from the scanner, parser, validator, and interpreter that are useful for users (and me!).

Do these things:

Write an errors.janet that's responsible for outputting nice errors
Produce the offending line
With a caret underneath that shows where the error is
And a more helpful (gentle) error message than what is produced in error objects
Add suggestions where helpful:
- Suggest bound names with an unbound name error
- Show actual place a name is bound one a name rebinding error
- Show function arities with arity mismatch
- Try to give a helpful reason for pattern mismatches
- Trace a panic!'s return path (instead of a stack trace, which is erased with TCO)

Stand up a system of presenting errors from the scanner, parser, validator, and interpreter that are useful for users (and me!). Do these things: - [x] Write an `errors.janet` that's responsible for outputting nice errors - [x] Produce the offending line - [x] With a caret underneath that shows where the error is - [x] And a more helpful (gentle) error message than what is produced in error objects - [ ] Add suggestions where helpful: - [ ] Suggest bound names with an unbound name error - [ ] Show actual place a name is bound one a name rebinding error - [ ] Show function arities with arity mismatch - [x] Try to give a helpful reason for pattern mismatches - [ ] Trace a `panic!`'s return path (instead of a stack trace, which is erased with TCO)