It says a lot about programming how far you can get with copy not reference, even though the base information often needs to be mutated and the whole point of the reference was to change state at the reference. But when code refactors and the need dies, you go on with things. So a missed ref -> copy is fine, contextually, for many people.
To this day I still get confused about what passes in some languages. the explicit &ref notation has merit of being clear.
It's not "one character change", but rather fixing an amateur mistake of passing by value instead of by reference.. but they have to frame it as a "win" which ironically is why enterprise engineering is so bad to begin with.
4 comments
[ 3.1 ms ] story [ 21.7 ms ] threadTo this day I still get confused about what passes in some languages. the explicit &ref notation has merit of being clear.