indygreg / indygreg/PyOxidizer
refactor error handling
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
Refactoring unwrap()/expect() into Result<> (or a better error handling primitive like using enums to handle multiple error types) might also be a good way to learn the codebase.
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 Rust codebase for unwrap() and expect() usages, then read the surrounding error paths to understand which failures need propagation or distinct handling. The issue does not name files, tests, or a settled design; done would require an agreed error-handling approach applied consistently across the relevant code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100