News for hackers. Stuff that matters.
Re:The .NET Language Strategy by hacker_9 on Wednesday February 01, 2017 @04:52PM (#13545662)
Probably the big one is non-nullable types [1], aka 'The Billion Dollar Mistake', which would break everything.

[1] https://gist.github.com/olmobrutall/31d2abafe0b21b017d56

Re:The .NET Language Strategy by hvidgaard on Thursday February 02, 2017 @07:06AM (#13549936)
If that is to be done, there needs to be some legacy settings for the compiler. I'll happily, trade inconvience for the ability to completely abolish null from my code. I already use a Maybe pattern to avoid returning null, but I cannot avoid checking for null because it's so ingrained in the standard lib.
Re:The .NET Language Strategy by smoothdeveloper on Thursday February 02, 2017 @01:26AM (#13548562)
Cobra language solved this and compiles to C#, they can introduce non nil references, but yes they can't scrap the BCL which is nil ridden.

Seems to go against null propagation operator though :)