Sorry, that made no sense, since the original message was not sent to the group. Here is the link:see https://github.com/golang/go/issues/11100-Original Message-
From: Robert Engels
Sent: Apr 3, 2019 12:36 PM
To: "Jason E. Aten"
Cc: golang-nuts
Subject: Re: [go-nu
The issue I linked to goes pretty in-depth on the reasons.
> On Apr 3, 2019, at 12:30 PM, Jason E. Aten wrote:
>
> Thanks Ian.
>
>> On Wednesday, April 3, 2019 at 6:57:32 PM UTC+2, Ian Lance Taylor wrote:
>> On Wed, Apr 3, 2019 at 8:34 AM Jason E. Aten wrote:
>> >
>> > Where does the
Thanks Ian.
On Wednesday, April 3, 2019 at 6:57:32 PM UTC+2, Ian Lance Taylor wrote:
>
> On Wed, Apr 3, 2019 at 8:34 AM Jason E. Aten > wrote:
> >
> > Where does the source for the runtime scheduler and garbage collector
> live these days?
>
> The central locations are runtime/proc.go and
On Wed, Apr 3, 2019 at 8:34 AM Jason E. Aten wrote:
>
> Where does the source for the runtime scheduler and garbage collector live
> these days?
The central locations are runtime/proc.go and runtime/mgc.go.
> Wherefore, I need to locate all runtime background threads and add in a means
> to
I don't know what you're trying to achieve but I think:
a. that it's not possible to have a program keep a consistent state while
enabling such behaviour
b. that there's a better way to do what you want to do
Maybe explaining (even vaguely) what your purpose is could help?
Le mer. 3 avr. 2019 à
Where does the source for the runtime scheduler and garbage collector live
these days?
Wherefore, I need to locate all runtime background threads and add in a
means to shut them down upon request.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts"
