MatMoore / MatMoore/string-inspector
DecodedCharacter::new should not panic
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Currently this can panic. But we should always be able to create a DecodedCharacter, even if the input is invalid.
May be fixed by https://github.com/MatMoore/string-inspector/issues/6
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
Start at the DecodedCharacter::new entry point and reproduce the panic with invalid input. Read issue #6 to determine whether it already addresses this case; done means invalid input can create a DecodedCharacter without panicking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100