On Wednesday, February 24, 2021 at 7:42:24 PM UTC-8 Bryan C. Mills wrote: > That said, that kind of coordinated release is *really* unpleasant, so > this is one of the motivating problems for https://golang.org/issue/36460 > (which I've been actively working on since basically the start of 2020). > I'm fairly confident that it will finally land in Go 1.17. After that — > when the dependencies of the affected modules become lazy, all of the > irrelevant dependencies of older-than-selected versions will just melt > away! (A gleaming future lies ahead!) >
I just saw that the new lazy code paths were enabled in tip. I'm sure there's still more to do before 1.17, but I know it's been a lot of work already and I wanted to say congrats and thanks... So, Bryan, congrats on landing this ~18 month behemoth and thanks for the gleaming future! -- 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/73ec684e-c5e1-46d2-a3a8-96200520f3d4n%40googlegroups.com.
