oxidecomputer / oxidecomputer/dendrite
want a more bespoke container for `PortRange`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 4
Description
In #334 we introduced PortRange, which gives us guarantees around the type. However, there's still room to improve how we store and search these PortRanges. We could have a container that enforces and makes use of these properties (e.g non-overlapping ranges) for storing and retrieving these entries. We should definitely look at implementations such as RangeSet/RangeMap.
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 reading the PortRange changes from issue #334 and investigate the RangeSet and RangeMap implementations mentioned here. Define and implement a container that enforces the relevant PortRange properties, such as non-overlapping ranges, while supporting storage and retrieval of entries.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100