If it was to be changed, it might be good to add the pair: Gomaxprocs() SetGomaxprocs()
I remember at the time it was suggested that it was "temporary API" that would go away someday. I have learned that there is rarely a temporary API, temporary utility, etc. On Fri, Dec 23, 2016 at 8:26 AM, Ian Lance Taylor <[email protected]> wrote: > On Fri, Dec 23, 2016 at 12:44 AM, P Q <[email protected]> wrote: > > runtime.GOMAXPROCS(n) behaves in two ways: getter if n < 1, otherwise > > setter. > > > > For setter, does runtime.SetGOMAXPROCS(n) look good? The only reason > behind > > current behavior is the function is rarely used? > > Does anybody actually make a mistake here? It's only worth fixing if > it is causing a problem. > > Ian > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Michael T. Jones [email protected] -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
