Skip to content

Conversation

sbomer
Copy link
Member

@sbomer sbomer commented Sep 6, 2025

Fixes #118713 (analyzer only for now)

Depends on #119291

@github-actions github-actions bot added the area-Tools-ILLink .NET linker development as well as trimming analyzers label Sep 6, 2025
@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label Sep 6, 2025
Copy link
Contributor

Tagging subscribers to this area: @dotnet/illink
See info in area-owners.md if you want to be subscribed.

Moving this warning is more complicated than that for base types
because we would either need to warn on conversion to interfaces,
or warn on every constructor (for kept interface implementations).
@sbomer sbomer changed the title Remove analyzer DAM warning on types Remove base DAM mismatch warning on types Sep 8, 2025
- Move new constraint processing to generic dataflow
- Take new constraint into account for requires dataflow check
MethodBodyScanner tracks known stacks by IL offset,
so these need to be correct when analyzing IL. We can't just
wait for cecil to update offsets for us when writing to disk.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Tools-ILLink .NET linker development as well as trimming analyzers linkable-framework Issues associated with delivering a linker friendly framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove DAM warning for base types/interfaces
1 participant