Curious warning

It appears that the #nullable disable directive only works if it comes after the using Statement.

vs

No big deal, but just curious as to why.

Comments

  • Presumably you have #nullable enabled by default. What will be happening is that the implicit #nullable enable is somehow ending up after the #nullable disable. This might be a side-effect of LINQPad having to extract the using directive and move it to the top of the generated C# code.