microsoft / microsoft/WinUI-Gallery
Which warnings should be enforced as errors for AOT?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.6k
- Forks
- 756
- Avg merge
- 17h 51m
- Merged PRs (30d)
- 14
Description
I'd like to start a discussion around which trimming and AOT-related warnings we should enforce as build errors by default.
When targeting Native AOT or enabling trimming, there are several warning categories—particularly ILxxxx, WMCxxxx, and CsWinRTxxxx—that indicate potential runtime issues (e.g. unsafe reflection, dynamic access, unsupported marshalling, or trimming-incompatible patterns).
⚠️ Candidate Warnings
The following warnings should be enforced as errors:
WMC1500, WMC1510, CsWinRT1028.
However, I'm uncertain about the ILXXXX warnings, as there are too many of them (~40), and it's unclear whether we should include all of them.
IL2000;IL2001;IL2002;IL2003;...;IL2123;
IL3000;...;IL3057;
FYI @marcelwgn
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 the warning categories and candidate list in issue #1992, focusing on WMC1500, WMC1510, CsWinRT1028, and the IL2000–IL3057 ranges. Determine which warnings should be enforced as build errors for trimming and Native AOT, then document the agreed policy; no file or test entry point is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100