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
Review usage of nullable suppressions (especially !) in CodeExporter.cs #78704
#78703 adds a couple of nullable suppressions that should be removed and cleaned-up. Those suppressions are necessary as previously, the assembly compiled against ref/System.CodeDom but with the above PR now binds against src/System.CodeDom which has a different nullability setting.
Winforms repo has problems as well with the current state of nullability annotations in System.CodeDom. We bumped into the same problems with CodeFieldReferenceExpression, CodePrimitiveExpression and CodePropertyReferenceExpression. See dotnet/winforms#9663
None of these suppressions are dangerous. The TypeReference! ones are genuinely non-null. The CodeDom API ones (null!) are correct usage that happens to conflict with CodeDom's lack of nullable annotations.
I'm still adding a PR to add some more Asserts and null-suppression cleanup for this file.
Activity
halgab commentedon Aug 5, 2023
Winforms repo has problems as well with the current state of nullability annotations in System.CodeDom. We bumped into the same problems with
CodeFieldReferenceExpression,CodePrimitiveExpressionandCodePropertyReferenceExpression. See dotnet/winforms#9663StephenMolloy commentedon Apr 27, 2026
None of these suppressions are dangerous. The
TypeReference!ones are genuinely non-null. The CodeDom API ones (null!) are correct usage that happens to conflict with CodeDom's lack of nullable annotations.I'm still adding a PR to add some more Asserts and null-suppression cleanup for this file.
Explicitly asserting CodeExporter beliefs about specific types of Dat…
Explicitly asserting CodeExporter beliefs about specific types of Dat…