Re: [go-nuts] Go's scheduler always “stuck” after certain time when executing the code below

> just add a function call occasionally depending on your required latency bound Thanks Jesper for your all detailed explanation. I quite agree with your point of view and conclusion. One thing left here should to be discussed is about the go scheduler's unwanted behaviour. Unwanted behaviour

Re: [go-nuts] Go's scheduler always “stuck” after certain time when executing the code below

On Wed, Jun 21, 2017 at 5:40 AM Ronald wrote: > Hi, I found when running this code below (play > ): > > > You are looking at a property of a specific Go implementation, not a property of the language. Any system must define a set of

[go-nuts] Go's scheduler always “stuck” after certain time when executing the code below

Hi, I found when running this code below (play ): package main import "fmt" import "runtime" import "time" type callRet struct { ret int } type callIn struct { ret_chan chan *callRet arg1 int } func caller(call_in_c chan *callIn, arg1 int) int { ret_c