3 ms·
Probably the big one is non-nullable types [1], aka 'The Billion Dollar Mistake', which would break everything. [1] https://gist.github.com/olmobrutall/31d2aba
by hacker_9 10y ago
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 https://gist.github.com/olmobrutall/31d2abafe0b21b017d56
- smoothdeveloper 10y agoCobra 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 :)
- hvidgaard 10y agoIf 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.