Someone forgot to set their phone to do not disturb
this is incredibly cursed. i love it.
I saw while(i --> 0) in someone else's code and thought wth is this --> operator? Then I realized it's while(i-- > 0) and thought cool, I gotta do this!
Isn't the evaluated value different from the expression? i++ returns the value of i before increasing. i-=-1 would return the value after it has been increased. Wouldn't it be more correct to make it equal to ++i
In the languages I know, i-=-1 or x=3 are not expressions, but rather statements, so they do not evaluate to a value.
So, this would be a compiler error:
a = (x=3)
Well, not all languages allow for fun programming :)
And that's why post- and pre-increment is non-existant in Python and Rust. It's an easy source for bugs for a noncritical abbreviationπ€·
They're especially also a source of bugs, because they encourage manually incrementing indices and manually accessing array positions, which is almost never actually sensible.
Takes 1 more character, that's bloat.
2 more
Thanks, i hate it
Someone forgot to set their phone to do not disturb
this is incredibly cursed. i love it.
I saw
while(i --> 0)in someone else's code and thought wth is this-->operator? Then I realized it'swhile(i-- > 0)and thought cool, I gotta do this!Isn't the evaluated value different from the expression?
i++returns the value of i before increasing.i-=-1would return the value after it has been increased. Wouldn't it be more correct to make it equal to++iIn the languages I know,
i-=-1orx=3are not expressions, but rather statements, so they do not evaluate to a value.So, this would be a compiler error:
Well, not all languages allow for fun programming :)
And that's why post- and pre-increment is non-existant in Python and Rust. It's an easy source for bugs for a noncritical abbreviationπ€·
They're especially also a source of bugs, because they encourage manually incrementing indices and manually accessing array positions, which is almost never actually sensible.