You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Incorrect IL2026 for [RequiresUnreferencedCode] on type deriving from A<B> where B has new() in A<T> definition #108507
Activity
dotnet-policy-service commentedon Oct 3, 2024
Tagging subscribers to this area: @agocke, @sbomer, @vitek-karas
See info in area-owners.md if you want to be subscribed.
sbomer commentedon Oct 3, 2024
Related: #108523
There are two problems here:
CA's ctor, notC.sbomer commentedon Oct 3, 2024
An additional problem we might want to solve as part of this:
In this case the analyzer misses the warning due to the implicit call to the base constructor. Note that the following example does produce a warning:
The logic for checking the new constraint should be moved into the analyzer's dataflow logic where the implicit base constructor call is visible.
Trim analyzer: fix member reported for generic warning (#108528)
Trim analyzer: fix member reported for generic warning (dotnet#108528)
Trim analyzer: fix member reported for generic warning (dotnet#108528)
sbomer commentedon Aug 15, 2025
This part was fixed in #108528.
Note that this wouldn't be a problem if we fixed #118713. I'm still planning to fix this independently though.
sbomer commentedon Aug 18, 2025
I extracted this to a separate issue so the fix can focus on the customer-reported scenario.
Suppress interface generic dataflow warnings under RUC (#131911)