News for hackers. Stuff that matters.
Re:Optimizing Go string operations with practical examples by marcus_holmes on Sunday December 03, 2023 @10:51PM (#38513536)
I love me some Go, but it is a gripe I have with the language; slice (and by extension string) allocation is opaque. There's no way of determining if two slices share the same underlying array, and no easy way of determining if an operation on a string will either cause the underlying array to be altered or cause the runtime to allocate a new array for the slice.

There are no comments on this comment yet.