That makes sense. Your excuse (just kidding) sounds like the one suggested
by Linux kernel developers about pluggable scheduler.
Just in case if you misinterpreted my intention. What I mean is not a
configurable GC by tuning the parameters, instead, just making it
replaceable by another one like a library. I wholeheartedly hate something
like conditional compilation macros too.

To be honest, it's very likely the Go designers will receive complaints
from some application no matter how good the default GC is.
On Tuesday, November 25, 2014 9:02:41 PM UTC+8, Jan Mercl wrote:

On Tue, Nov 25, 2014 at 1:40 PM, <aruma...@gmail.com <javascript:>>
My plan is to refactor the runtime to an extent so that the GC can be
Go designers avoided most GC knobs, modulo debugging stuff, for a good
reason. Once Go programs start to work terribly under particular load
without being given specific values of GC knobs, that reason will
proven again.

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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 23 of 32 | next ›
Discussion Overview
groupgolang-nuts @
postedNov 24, '14 at 4:39p
activeNov 26, '14 at 4:35a



site design / logo © 2022 Grokbase