MaxiTB

One thing that always bugs me is that I haven't found yet a way to make static code analysis of nullable ref types work over inheritance boundaries - is there already a way available in #dotnet #csharp to solve this issue in a clean way with attributes?

https://sharplab.io/#v2:C4LghgzgtgPgAgJgIwFgBQ64GYAEYBGEwATmAMbA6I4BCkApugN7o5tW5wAsOAogB70yAV2D0AFAEpW7FmnYKcABWL0ADmFVSA3DMVUkATnEBZMGqmTd89gF89OB2uIB7MRXoATPIRLlK3MqqGlpWDgpOru5i3gREpBQGAAw4ZhZhaPYYaNg4EPRgADZeVAg4AMr0xABuAJZk9DggtAzMkW5CMTgu1VXEtZ6NgSrqmhLSNmxy+mwA+gB2YFCNALw4AEQAEvSFhS44AOouxIWe69YKWe3RJT19A0NIKWlSDtMzcADsOAtL9No4AD0gJwAEkIDhgAALKqNMA4ADuYAAnpD9nAkAA2IqFVEAc3olH63hcADNITCcH1jojatCXKIqCkMSlfsscGt5sJdgBCHAAfgcV0mOGctWqYDEyX5P0Wy2stiAA==

SharpLab

C#/VB/F# compiler playground.

Nov 23, 2024 at 11:24amWeb
Show threadKris VandermottenNov 23, 2024
@maxitb
Debug.Assert(_name != null);
Show threadMaxiTBNov 23, 2024
@kvandermotten Oooh, that's a neat trick - I always thought that nullability code analyzers respect the Conditional attribute but they actually don't.