oxidecomputer / oxidecomputer/ingot
`NetworkRepr` should be fallible
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This ties into the validity checking piece (#2) somewhat -- while typically the design of ingot encourages newtype wrappers and associated constants to handle unrecognised values, in some cases we need to safely account for values being truly unrepresentable.
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
Start by locating the NetworkRepr implementation and reading the related validity-checking issue (#2). Determine which values are unrepresentable and what fallible behavior the API should expose; the work is done when that behavior is specified, implemented, and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100