News for hackers. Stuff that matters.

A comment on Why Dart is not the language of the future.. Parent comment

Re:Why Dart is not the language of the future. by bad_user on Tuesday October 11, 2011 @03:46PM (#3100015)
Considering this is a new language, why allow nullable references in the first place? What you call good practice I actually consider a curse.
[ Parent | on HN ]
Re:Why Dart is not the language of the future. by ohyes on Tuesday October 11, 2011 @04:23PM (#3100146)
I 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.

[ Parent | on HN ]
Re:Why Dart is not the language of the future. by rat on Wednesday October 12, 2011 @03:58AM (#3101938)
Don'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

[ Parent | on HN ]
Re:Why Dart is not the language of the future. by dhugiaskmak on Tuesday October 11, 2011 @04:06PM (#3100092)
It 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.
[ Parent | on HN ]
Re:Why Dart is not the language of the future. by fpgeek on Tuesday October 11, 2011 @10:02PM (#3101181)
Tony Hoare's case wasn't good enough?

http://qconlondon.com/london-2009/presentation/Null+Referenc...

[ Parent | on HN ]