enlightware / enlightware/ferlium
Improve TypeMismatch errors when match exhaustiveness fails
Open
error messages
- Dominant language
- Rust
- Stars
- 14
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
A first step in that direction is to add context to `TypeMismatch` error sand write some more useful error messages when match exhaustiveness fails.
Contributor guide
Research direction
Start by locating the TypeMismatch error definition and the code handling match exhaustiveness failures. Read how these errors are currently constructed, then define completion as adding context to TypeMismatch and producing more useful messages for failed exhaustiveness checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100