oxidecomputer / oxidecomputer/hubris
packrat: Consider reworking "cfg sprawl"
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
The packrat task has a lot of #[cfg]s (64 instances of #[cfg at the time of this writing). I'm about to add a bunch more for metro support.
It might be worth giving it a treatment similar to #2683 to make the similarities and differences between boards more clear.
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 by reading the packrat task and issue #2683, then inspect the existing #[cfg] uses and the additional metro-related configuration. Determine how the board similarities and differences should be represented. The work is done when the configuration structure is clearer without losing the required board support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, operating-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100