[go-nuts] C program calling a buildmode=c-shared shared object, which calls a plugin.

I have a C program that calls into a Golang shared object (built using -buildmode=c-shared). That works. Now I want the Golang shared object to call out to a Go plugin (using https://golang.org/pkg/plugin/), but plugin.Open panics with "fatal error: runtime: no plugin module data": runtime.th

[go-nuts] Concurrent and blocking stack

Hi everyone, I have this mock interview question, "How would you implement concurrent and blocking stack and queue in Go?" which I have no idea on how to answer it. If anyone can guild me -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsub

Re: [go-nuts] Re: Language is a platform, which golang still does not pay attention to !!!

The question of "what does Go learn/take from C++" is subtle. I claim that Go takes everything the authors value in the change from C to C++. On Fri, Apr 6, 2018 at 9:42 PM, T L wrote: > > > On Friday, April 6, 2018 at 11:24:20 PM UTC-4, Hoo Luu wrote: >> >> >> >> 在 2018年4月7日星期六 UTC+8上午12:48:56，

Re: [go-nuts] Re: About a channel detail, bug, defect, or intended?

On Saturday, April 7, 2018 at 9:04:38 AM UTC-4, T L wrote: > > > > On Saturday, April 7, 2018 at 8:39:22 AM UTC-4, Steven Hartland wrote: >> >> You should use a wait group to guarantee the behaviour of this. >> > > I know there are other ways to do the task. > I just feel the runtime behavior is

Re: [go-nuts] Re: About a channel detail, bug, defect, or intended?

On Saturday, April 7, 2018 at 8:39:22 AM UTC-4, Steven Hartland wrote: > > You should use a wait group to guarantee the behaviour of this. > I know there are other ways to do the task. I just feel the runtime behavior is some strange. The following is the code to receive a value if there are so

Re: [go-nuts] Re: About a channel detail, bug, defect, or intended?

You should use a wait group to guarantee the behaviour of this. On Sat, 7 Apr 2018 at 12:54, T L wrote: > > > On Monday, March 26, 2018 at 4:09:24 PM UTC-4, Marvin Renich wrote: >> >> It seems that you understand why you are seeing the behavior you >> reported, but you are questioning whether th

Re: [go-nuts] Re: About a channel detail, bug, defect, or intended?

On Monday, March 26, 2018 at 4:09:24 PM UTC-4, Marvin Renich wrote: > > It seems that you understand why you are seeing the behavior you > reported, but you are questioning whether the spec either does or should > guarantee that reading from a channel with a goroutine waiting to send > on that