On Thursday, December 12, 2019 at 3:53:07 PM UTC+1, Bryan C. Mills wrote:
>
> This is a bit off-topic now, but coincidentally we will have another talk
>> (probably by my work colleague) that is related to one of your approaches
>> from the talk:
>>
>> // Glob finds all items with names matching
to understand when you start with
>> solutions. I think maybe clearly restating the problem will allow more
>> people to offer up ideas. To be honest at this point I’m not really certain
>> what you’re trying to demonstrate or why.
>>
>> On Dec 8, 2019, at 12:44 AM, Eg
Interesting suggestion, but I added the implementation with buffer = 1 here
and it still deadlocks:
https://github.com/egonk/chandemo/blob/master/2_3.go#L5
It stopped deadlocking when buffer = 5, so I think it will be a nice lesson
about hiding design problems with buffers. Did you have somethi
ency-test) but that is
> not what you are attempting here... you are using async processing - these
> are completely different things. Using async in Go is an anti-pattern IMO.
>
> On Dec 8, 2019, at 12:11 AM, Egon Kocjan >
> wrote:
>
>
> I'll cite myself:
> &quo
t; (which it looks like you’ve tried) but why???
>
> It’s like saying I’d really like my plane to float - you can do that -but
> most likely you want a boat instead of a plane.
>
> On Dec 7, 2019, at 2:38 AM, Egon Kocjan >
> wrote:
>
>
> I'll try to clarify
I think you might be encountering a deadlock because the producer on one
> end is not also reading the incoming - so either restructure, or use 2 more
> threads for the producers.
>
>
>
> On Dec 6, 2019, at 10:38 PM, Egon Kocjan >
> wrote:
>
> Agreed, I see goro
e:
>
> A channel is much closer to a pipe. There are producers and consumers and
> these are typically different threads of execution unless you have an event
> based (async) system - that is not Go.
>
> On Dec 6, 2019, at 9:30 AM, Egon Kocjan >
> wrote:
>
>
>
hannels are designed to be used with multiple go routines - if you’re not
> you are doing something wrong.
>
> On Dec 6, 2019, at 8:32 AM, Egon Kocjan >
> wrote:
>
>
> Hello
>
> I'm preparing a short talk about Go channels and select. More
> specifically, I wan
Hello
I'm preparing a short talk about Go channels and select. More specifically,
I want to show what not to do. I chose a bidirectional communication
channel implementation, because it seems to be a common base for a lot of
problems but hard to implement correctly without using any extra
goro
