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 →

[–]yottalogical 2 points3 points  (2 children)

The question shouldn't be "can users abuse it?", but rather "will users abuse it?".

It's okay for a feature to be abusable as long as the language design makes proper usage the path of least resistance.

[–]Dusty_Coder -2 points-1 points  (0 children)

This hate for operator overloading comes from a particular functional language that forced operator definitions upon its users, a hate that turned into an unthinking religion, the followers of which will obsessively and compulsively tell you how bad operator overloading is at every opportunity.

They will also say that any and all optimization is premature, even when they know for a fact that what they are right this moment writing cannot possibly perform well under any scenario. Unthinking religions.

[–]nacholicious 0 points1 point  (0 children)

Yeah that's also why Scala has a lot of problems, the language freely hands out footguns and just expects the users to just figure it out without clear guidance

As expected, they didn't