On Wednesday, 12 February 2020 22:57:04 UTC, robert engels wrote: > > (Or even Go's GC performance progression - but as I mentioned, in this > particular test the lack of a generational collector is holding it back). > > This is discussed in great detail here: https://blog.golang.org/ismmkeynote
<https://blog.golang.org/ismmkeynote> TL;DR: generational GC for go has been done, but for various reasons which that presentation goes into, it turns out to be worse in some important cases than the status quo. -- 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/db67b764-905a-4ebf-b61c-ccd06aff4f6e%40googlegroups.com.
