The shorthand I use for "becomes the same as" is "gets".
My CS professor (~ola) taught it as "gets" and to this day when I talk out code people get confused. I'll say, "x gets 3" and they look at me funny. But I find it helpful for differing between assignment and equality.
Re:Why Does “=” Mean Assignment?
by noonespecial on Tuesday April 10, 2018 @10:26PM
(#16807560)
I never liked the 'gets':
"x gets 7" is fine but
"x becomes the same as y" seems better than "x gets y"
that's wrong, though. x becomes a copy of y, which is only transiently the same.
What is "transiently the same"?
Genuinely asking - my first thoughts are:
"transiently the same" is not the same as "the same", hence it is not "the same", and therefore "not the same".
No jokes on the meta-level please :o)
Depends on the language, and the types of x and y. See e.g. python.
We read it out loud as "becomes the same as", this being what was actually happening. I've carried the habit over to C despite the bare =, it helps me reason and seems to aid in preventing the =/== error.