News for hackers. Stuff that matters.
Re:Understand Go pointers by agentgt on Wednesday April 26, 2017 @01:11PM (#14204918)
Because Rust is not a GC language. I should have perhaps explained that better. My round about point mentioning Rust was that instead of putting "*" all over the place you could just have types that represent such (pointers) or the opposite (ie value types) depending on what the language defaults to. I mean the pointer in some senses is effectively abstract wise Pointer<SomeType>. However I suppose this is difficult with out generics.

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.

Re:Understand Go pointers by mixedCase on Wednesday April 26, 2017 @01:23PM (#14205032)
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.

Re:Understand Go pointers by agentgt on Wednesday April 26, 2017 @01:39PM (#14205178)
> Implicit pointers means you have to often think extra when shuffling data structures around.

This basically answered my question. Thank you. I don't know why I didn't make that connection.