Re: [go-nuts] GO routine never exits based on stop condition - unable to find the reason

Great, thanks! On Mon, 28 Mar 2022 at 12:53, Steven Hartland wrote: > No problem, there's a nice little write up on it stackoverflow > <https://stackoverflow.com/questions/47645808/how-does-select-work-when-multiple-channels-are-involved> > . > > On Mon, 28 Mar 2022 at 17:4

Re: [go-nuts] GO routine never exits based on stop condition - unable to find the reason

: > There is no guarantee that the select chooses the done case, so you need > to check in work case as well e.g. > https://go.dev/play/p/zAj_qfO4uMA > > On Mon, 28 Mar 2022 at 16:54, Gowtham Raj wrote: > >> In this example, we have a *worker*. The idea here is simulate clean >> shu

[go-nuts] GO routine never exits based on stop condition - unable to find the reason

In this example, we have a *worker*. The idea here is simulate clean shutdown of all go routines based on a condition. In this case, go routines get spun - based on workers count. Each go routine reads the channel, does some work and sends output to the outputChannel. The main go routine

[go-nuts] Thread ID in glog

Hey! In this line , are you planning to change pid to thread ID? I would like to use glogs to display different IDs for each worker thread. Thanks, Ramya -- You received this message because you are

[go-nuts] vgo tooling support

vgo is still in proposal state. https://github.com/golang/go/issues/24301. I believe tools start supporting it once it accepted, finish the implementation and released may be as part of Go1.11. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group.

[go-nuts] Re: [ANN] A Go based map reduce system (second attempt)

>> However, it is still limited by the fact that Go code can not be sent and executed remotely. I am not sure if this makes the situation better for this particular use case, but I see that David Crawshaw is working on plugin mode for Go. It looks like it will be part of Go1.8. -- You

Re: [go-nuts] Speeding up multiple regexp matches

But that won't give me list of all matched regexps. No? On Thursday, July 28, 2016 at 12:32:41 AM UTC-7, Tamás Gulácsi wrote: > > Just concatenate them with |. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and

[go-nuts] Re: Speeding up multiple regexp matches

- There are more than 10,000 regexps. - I need to do this task on ~ 800 million strings having max length 1KB each, and this number growing daily. - Currently regular expressions are simple. It's actually what MS SQL Server like operator supports. i.e. "_%[]^". See

[go-nuts] Speeding up multiple regexp matches

Not specific to golang. Incidentally I am using go to develop this particular tool. I have a piece of text that I want to test against a large number of regular expressions, where a different action is taken based on which regexps successfully matched. The naive approach is to loop through

Re: [go-nuts] Re: golang sql driver: bad connection

On Friday, July 8, 2016 at 11:16:50 PM UTC+5:30, Konstantin Khomoutov wrote: > > On Fri, 8 Jul 2016 08:15:27 -0700 (PDT) > Raj <rajenderre...@gmail.com > wrote: > > > Initially the program giving err driver: bad connection for rows.Err > > (). So I added panic wi

Re: [go-nuts] Re: golang sql driver: bad connection

On Fri, Jul 8, 2016 at 7:50 AM, Raj <rajenderre...@gmail.com > > wrote: > > By the way I am using go1.7 beta2. Same error was appearing with go1.6 > also. > > > > What does those 8 minutes mean in stack trace? > > Those annotations mean that thos