Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
== and === #42
Looks like another step towards more Ruby-like and expressive syntax would be:
This is helpful when comparing values, which we are in most common cases
Thiw would map Java's standard behaviour it to Mirah's, without changing how it works.
We could do it Ruby style--where == usually delegates to equals, eql? and equal? are used for object identity and === does the sensible thing for a case statement.
We don't have case statements currently, but we should try to figure out whether we want them to act like Ruby's case or like Java's switch.
"Comment 3 by ndh.000...@gmail.com, May 22, 2011
do we want to follow Ruby or introduce a different thing?
Comment 4 by michal.h...@gmail.com, May 22, 2011
I'd go with == and === for comparisons.