oxidecomputer / oxidecomputer/ingot
Want test cases `expectorate`ing example generated code
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
One of the downsides to making use of proc-macros is that, barring the use of cargo expand, generated code is fairly opaque. It would be nice to have changes in output code meaningfully shown (and asserted) as part of CI.
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 exploring the repository's proc-macro entry points and use cargo expand to inspect the generated code. Determine a suitable way to show meaningful output changes and assert them in CI; done means generated-code changes are visibly reviewed and covered by automated tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100