Implement error reporting
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Good error reporting is important for any language and especially ones that might be used by people who aren't programmers.
For this reason I think a lot of our focus should be on this. I suggest implementing an ErrorReport struct that serves as a builder allowing for configurations such as adding errors, sources, source path etc. and should be able to write the report to any T: Write.
Contributor guide
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
The issue names no files, tests, or existing entry points. Start by locating the parser's current error paths and usages of Rust's Write trait. Done means an ErrorReport builder can add errors, sources, and a source path, then write the resulting report to any T: Write.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100