4 ms·
> It's memory safe due to the GC That gets debatable as soon as you start using concurrency, like I said. There are idiomatic patterns in concurrent Go that ar
by zozbot234 7y ago
> It's memory safe due to the GC
That gets debatable as soon as you start using concurrency, like I said. There are idiomatic patterns in concurrent Go that are very much not safe.
- MaxBarraclough 7y agoWhat do you mean? It has a GC, right? So use-after-free is impossible, no?
- petjuh 7y agoSerious question - has that been verified, especially with regards to concurrency? Also does it rely on the assumption that GC implementions such as Java's are bug-free in this regard, and if so - has that been verified as well?