News for hackers. Stuff that matters.
Re:Announcing Rust 1.22 by cesarb on Thursday November 23, 2017 @05:39AM (#15764205)
In C, the value of x in that fragment is still the same: a pointer (ok, not exactly, but something which behaves like a pointer) to a memory location where an int can be stored. The f(x) call can't change that pointer.
Re:Announcing Rust 1.22 by int_19h on Thursday November 23, 2017 @06:21AM (#15764364)
Try doing something like &x, and you'll see that it doesn't actually reliably behave like a pointer.