3 ms·
Considering this is a new language, why allow nullable references in the first place? What you call good practice I actually consider a curse.
by bad_user 15y ago
Considering this is a new language, why allow nullable references in the first place? What you call good practice I actually consider a curse.
- dhugiaskmak 15y agoIt was hinted in one of the other Dart threads here (or maybe on reddit) that if enough people got on the mailing list and made a good, reasoned case for it that null could still go away.
- fpgeek 15y agoTony Hoare's case wasn't good enough? http://qconlondon.com/london-2009/presentation/Null+References:+The+Billion+Dollar+Mistake http://qconlondon.com/london-2009/presentation/Null+Referenc...
- ohyes 15y agoI agree that it would be better to not compare a null reference at all. A better option would be to return multiple values or have a tuple type and pattern matching. Like I said, I'm not particularly a fan of Dart.
- rat 15y agoDon't (typed) Union types work better for errors(with pattern matching) In haskell I think a nullable type or possibly error type frequently returned from functions which can error ie. data Maybe a = Nothing | Just a data Either a b = Left a | Right b instead of (err,result) like in go