Handle scenarios when the transitive closure of types is known.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 665
- Forks
- 134
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
There are scenarios in WinRT where the transitive closure of all types is known. This would imply there are opportunities to optimize the RCW code generation logic and avoid querying the runtime for these types - see https://github.com/microsoft/CsWinRT/blob/4e73245f7465e3adf2ec4cbcfe0e54e9cc988786/cswinrt/strings/WinRT_Wrappers.cs#L121
Reasons for considering this are: AOT and linkability (reduce memory footprint).
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 with cswinrt/strings/WinRT_Wrappers.cs around line 121 and trace the RCW code generation logic that queries the runtime for type information. Investigate how known transitive closures relate to AOT and linker behavior. Done means the applicable scenarios avoid unnecessary runtime queries while preserving correct RCW generation and reducing the footprint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100