Jump in the discussion.

No email address required.

Vile. These operators are an important tool. If the new dev doesn't use them (and he usually doesn't) I know he's r-slurred.


https://i.rdrama.net/images/172187329668082.webp

Jump in the discussion.

No email address required.

mutation is evil

i'd rather stick my object in your butt than frequently need to iterate random numerical variables because I dont know how to use map or functional accumulators

Jump in the discussion.

No email address required.

A reminder to all programmers: any and all mutable things with a wide scope will eventually be destroyed by an H1B. If you expose it, it will one day by incremented by 1 in an edge case.

Murphy's law :marseyno:

Curry's law: “What can be mutated by an Indian will be mutated by an Indian”

Jump in the discussion.

No email address required.

In like 80% of cases I use x += 1 because I think it's much more clear.

Jump in the discussion.

No email address required.

>not refactoring all your code to use a custom Increment(x) function

Brainlet detected

Jump in the discussion.

No email address required.

>not generalizing to MutateByRef(&x, sizeof(x), MutationImplIncrementFactory.NewInstance(1))

Jump in the discussion.

No email address required.

:marseykneel:

Jump in the discussion.

No email address required.

You might as well put x = x +1 at that point :marseygigaretard:

Jump in the discussion.

No email address required.

This is superior than ++, ++ should only be used in c type for loops which should also be avoided unless youre optimizing for performance or doing weird shit

Jump in the discussion.

No email address required.

Craziest part is that it seems the person that's responsible for the change was Chris Lattner of all people.

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.