3 ms·
As Carmack points out, naming the intermediate values aides in debugging. It also helps you write code as you can give a name to every mutation. But also keep
by jayd16 1y ago
As Carmack points out, naming the intermediate values aides in debugging. It also helps you write code as you can give a name to every mutation.
But also keep in mind that correct and incorrect is not binary. You might want to pass a fooA to another class that does not want the fooB mutation.
If you just have foo, you end up with situations where a copy should have happened but didn't and then you get unwanted changes.
- ErroneousBosh 1y agoBut that's just it, why would a copy ever happen? Why would you want a correct and an incorrect version of your variable hanging about?
- kubanczyk 1y agoTaking your point of view: you assigned a value1 to a name. Then you assigned a value2 to the same name. You say that value2 is correct. It logically follows that value1 was incorrect. Why did you assign it then? The names are free, you can just use a correct name every single time.
- zaphirplane 1y agoBecause the account owner withdrew money . The player scored a goal, the month ticked over, the rain started, the car accelerated, a new comment was added to the thread . The world by definition mutates over time.
- kubanczyk 1y agoAh, true. If the var is a part of a long-living state, all good. That's just rarely seen in CRUD apps, more common in games.