Re:Updating the Go Memory Model
by ryanschneider on Monday July 12, 2021 @12:48PM
(#27812253)
The thing that has bitten me the most is somewhat related: the lack of any uniform “deep copy” or immutability support. Sure I can make a `chan Foo` but if Foo is a struct with an embedded pointer in it you just aliased a pointer you probably didn’t mean to.
If there was supported for optional value types rather than using pointers that would help too.
If there was supported for optional value types rather than using pointers that would help too.