Re:Google broke a conditional statement that verifies passwo...
by tialaramex on Thursday July 22, 2021 @10:10PM
(#27926485)
Yeah. The direction of modern languages has been away from features like this which are "clever" but don't express anything you couldn't have said by another means - and yet allow programmers to accidentally write something nobody would ever want.
Assignment shouldn't have a return type. Compound assignment operators? Likewise. You never need this return value, and sometimes you may use it by mistake. So, abolish it. In C++ not only do operators that shouldn't have a return value have one anyway, the type of that value might be anything. You can even overload both ++ operators to return different unrelated types so that
mytype aThing { blah };
auto a = aThing++; // returns a String "Fuck tha police"
auto b = ++aThing; // returns a double, 8.63
The Jeff Goldblum GIF is often the appropriate reaction to C++ features:
"Your scientists were so preoccupied with whether or not they could, that they didn't stop to think if they should"
Assignment shouldn't have a return type. Compound assignment operators? Likewise. You never need this return value, and sometimes you may use it by mistake. So, abolish it. In C++ not only do operators that shouldn't have a return value have one anyway, the type of that value might be anything. You can even overload both ++ operators to return different unrelated types so that
The Jeff Goldblum GIF is often the appropriate reaction to C++ features:"Your scientists were so preoccupied with whether or not they could, that they didn't stop to think if they should"