On Friday, May 14, 2021 at 10:28:24 AM UTC-4 Michael Pratt wrote: > Go has a non-moving GC [1], so that is not an issue. > It is my understanding that the go team has always explicitly maintained the 'right' to change the GC to allow moving memory. Or to allow another implementation of the Go language to do so. That is the purpose of some of these rules. So if you write code that assumes a non-moving GC, then be prepared for breakage later.
I know that the standard libraries do things that violate those rules, because they are tied to the Go version they ship with. So the Go team will adjust them as necessary when changes are made to Go. I am not entirely clear if this logic applies to the golang.org/x libraries as well. > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/2df2d684-0c12-4697-ab9e-568bf97870c1n%40googlegroups.com.
