@dsyme @migueldeicaza Are there good examples of how it's a big time saver? i.e. is it just the elimination of null checks?
-
-
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 -
Replying to @demisbellot
@demisbellot It does all circle back to@migueldeicaza 's initial query. If we could eliminate null in C#, then things are much better IMO.2 replies 0 retweets 0 likes -
Replying to @simpleprogrammr
@jsonmez Definitely not a fan of removing them, there's useful stuff like optional params + complex object requests that would be hard w/o.1 reply 0 retweets 0 likes -
Replying to @demisbellot
@demisbellot Well I certainly could be wrong. I often am, just my opinion at the time. :)1 reply 0 retweets 0 likes -
Replying to @simpleprogrammr
@jsonmez Oh I'm not sure what Miguel thinks, I meant *I* wasn't a fan of complete annihilation, just sand-boxing + curation :)1 reply 0 retweets 0 likes
@demisbellot Yeah, I think you are right. I tend to be extremist, sand-boxing + curation is probably better than elimination.
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.