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?
-
-
Replying to @migueldeicaza
@migueldeicaza All solved at the langauge level by the F# design. nulls are abnormal except for C# types. Such an enormous time saver4 replies 1 retweet 1 like -
Replying to @dsymetweets
@dsyme@migueldeicaza Are there good examples of how it's a big time saver? i.e. is it just the elimination of null checks?1 reply 0 retweets 0 likes -
Replying to @demisbellot
@demisbellot@dsyme not ever having a nullref exception1 reply 0 retweets 0 likes -
Replying to @migueldeicaza
@migueldeicaza@demisbellot@dsyme my take from a while back:http://elegantcode.com/2010/05/01/say-no-to-null/ …1 reply 1 retweet 1 like -
Replying to @simpleprogrammr
@jsonmez How can moving null checks to the call sites result in less code? Sounds counter-intuitive, got examples showing less code?3 replies 0 retweets 0 likes -
Replying to @demisbellot
@demisbellot So basically, you try to make things immutable and always initialized to a valid value. Null object pattern helps as well.2 replies 0 retweets 0 likes -
Replying to @simpleprogrammr
@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.2 replies 0 retweets 0 likes
@demisbellot Code Contracts static analysis can actually detect if your code could ever create a NRE.
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.