oxidecomputer / oxidecomputer/typify
Enum Name Collision
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 898
- Forks
- 114
- Avg merge
- 4h 18m
- Merged PRs (30d)
- 14
Description
In the Vega example, an enum with __count__ and count outputs:
pub enum AggregateTransformOpsVariant0ItemVariant0 {
#[serde(rename = "count")]
Count,
#[serde(rename = "__count__")]
Count,
// ...
}
I'm looking into whether __count__ is a spec bug and not meant to be exposed 😅 , but from a code gen perspective figuring out what to do with these collisions is probably worthwhile.
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
Reproduce the Vega example and inspect the code-generation path that turns the colliding enum values into Rust variants. First determine the intended handling for count and __count__, including whether the schema exposes both values. Done means the chosen collision behavior is implemented and covered by a regression test for this example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100