On Thu, Nov 1, 2018 at 2:58 PM, Michael MacInnis
wrote:
>
> On Thursday, November 1, 2018 at 12:20:39 PM UTC-4, Ian Lance Taylor wrote:
>>
>>
>> Every blocking cgo call requires a thread. Also every Go program has
>> a supporting thread that monitors the programs. If you see only 4
>> threads fo
On Thursday, November 1, 2018 at 12:20:39 PM UTC-4, Ian Lance Taylor wrote:
>
>
> Every blocking cgo call requires a thread. Also every Go program has
> a supporting thread that monitors the programs. If you see only 4
> threads for that program then I think we're doing pretty well.
>
> Ian
On Thu, Nov 1, 2018 at 7:24 AM, Michael MacInnis
wrote:
>
> While running a Go program that uses Cgo, I noticed a surprising number of
> threads. I believe the code below demonstrates what I'm seeing minus (what I
> hope are) extraneous details.
>
> package main
>
> // #include
> import "C"
>
> f
While running a Go program that uses Cgo, I noticed a surprising number of
threads. I believe the code below demonstrates what I'm seeing minus (what
I hope are) extraneous details.
package main
// #include
import "C"
func main() {
for {
C.nanosleep(&C.struct_timespec{tv_sec: 0, t
