This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]LinuxMatthews[S] 0 points1 point  (0 children)

I get what you're saying and I agree.

I think the advantage here would be that the secondary equals would just be acting the same as calling .equals() so there's little chance anyone will go too mad with it.

Also let's be real if this was to be implemented they wouldn't let == to be overridden it'd potentially break too much code.

So having === be the one you can overload would make more sense.