Hacker News Reader

The author definitely understands that. The point is: when you don't have operator overloading you get stuff like that which does demonstrably confuse many people

In languages with operator overloading this just isn't a concern at all because == does the obvious thing

View on HN

> In languages with operator overloading this just isn't a concern at all because == does the obvious thing

And what is the obvious thing? It varies wildly among languages, even within C++ itself.

The obvious thing is to check if the contents are equal. I don't know what cursed C++ you're looking at if you're finding a ton of string implementations not doing exactly that...

== should do the obvious thing. But with operator overloading, it's not clear that it does, unless you need to read the implementation of == very carefully.

How is that any different to some opaque method call? By the same logic `a.equals(b)` might be doing something funky under the hood

True. But people think about it a bit differently. People don't always expect == to be a function call.

Sure, but I think '== might be a function call' is a lot less confusing than '== sometimes compares for equal value and sometimes doesn't'

Reply on news.ycombinator.com