Add `ParseError.description() -> &'static str` method like already implemented on `SyntaxViolation`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 406
- PR merge metrics
- No merged PRs in 30d
Description
Would be great, so we don't need to allocate a string for something which is fundamentally static.
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
Search the repository for ParseError and the existing SyntaxViolation::description implementation. Compare their error descriptions and verify that ParseError exposes the requested static description without allocating; add focused coverage alongside the existing error tests if that test location is found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100