microsoft / microsoft/windows-rs
`windows-core` consolidate `Param`/`Ref`/`InterfaceRef` etc
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 12.8k
- Forks
- 665
- Avg merge
- 7h 9m
- Merged PRs (30d)
- 70
Description
A number of conversion types and traits have been developed to solve different problems. Some like `Param` are used by `windows-bindgen` while others are more suitable for hand-authored APIs. It's just a bit confusing and hard to know what the right tool is where there are so many options.
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 in the windows-core conversion types and traits, comparing Param, Ref, and InterfaceRef with their use by windows-bindgen and hand-authored APIs. Map the overlapping roles and document which options should remain or be consolidated. Done means the API choices are simpler and the appropriate tool is clear for each use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100