It's not so much about what's optimal for performance but as to which piece of state changes and which one doesn't.
Implicit pointers means you have to often think extra when shuffling data structures around.
Implicit pointers means you have to often think extra when shuffling data structures around.
That is I don't mind the explicitness of Rust because I guess I expect it just like C/C++ but I probably incorrectly expect it with Go lang. This is mostly because I come from a JVM background where I expect the VM to figure out what is more optimal and consequently also have very little experience using in/out parameters.