ParseError needs to communicate the index into the string or the span where the error happened
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 110
- Forks
- 14
- Avg merge
- 16h 45m
- Merged PRs (30d)
- 1
Description
This issue has no description.
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
The issue names ParseError but provides no files, tests, or implementation details. Start by locating ParseError and the parser entry points, then determine how an error can report its string index or span. Done means the chosen error location is communicated consistently and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100