4 ms·
I think it's because go's community sticks close to the standard library: e.g. iirc. Rust has multiple ways of handling Strings while Go has (to a big extent)
by tzekid 1y ago
I think it's because go's community sticks close to the standard library:
e.g. iirc. Rust has multiple ways of handling Strings while Go has (to a big extent) only one (thanks to the GC)
- adastra22 1y agoWhat does String/OsSfeing have to do with garbage collection?
- diarrhea 1y ago> Rust has multiple ways of handling Strings No, none outside of stdlib anyway in the way you're probably thinking of. There are specialized constructs which live in third-party crates, such as rope implementations and stack-to-heap growable Strings, but those would have to exist as external modules in Go as well.