Someone wrote a detailed analysis of why it was not easy to extend C# to support not-null, ie, print (string! msg), anyone have a link?
-
@jsonmez How can moving null checks to the call sites result in less code? Sounds counter-intuitive, got examples showing less code?
@demisbellot So basically, you try to make things immutable and always initialized to a valid value. Null object pattern helps as well.
-
-
@jsonmez Unless it's guaranteed not to be null, i.e. I can see how you can get away with it in F# since guarantees are baked into the lang. -
@demisbellot It does all circle back to@migueldeicaza 's initial query. If we could eliminate null in C#, then things are much better IMO. - 4 more replies
New conversation -
-
-
@jsonmez I prefer doing that for multi-threaded code, but code is only as strong as the weakest link. Seems wrong to create libs w/o checks. -
@demisbellot I agree, for libraries you really have to check, but once inside your gates, you can write code that is never null.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.