1. 7
    1. 2

      Saw this concept before in other contexts, but now that I see it again… doesn’t it come down to “we want to tune the GC’s collection rules but its API won’t let us”? All you’re REALLY saying is “hey GC, go ahead and use more memory… it’s fine.”

      In other words, it’s one of the problems I’ve had with GC’s before… Not being able to tune it sufficiently. Anyone have any examples out there of really good GC API’s?

    2. 2

      This technique should be obsolete in Go 1.19. It introduces features to set memory limits.