oxidecomputer / oxidecomputer/netadm-sys
Consider moving `ioctl` and `ioctl_ro` from macros to generic functions.
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
See discussion in #18.
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 discussion in issue #18, then locate the ioctl and ioctl_ro macros in the repository. Determine from that discussion what generic-function API is expected and what compatibility constraints apply. Done means the agreed design is implemented and the existing behavior remains covered by the project's tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100