Because the arguments are evaluated when the go keyword is encountered - and
listen and serve is blocking on port 8082
> On Feb 18, 2022, at 10:38 AM, Christoph Berger
> wrote:
>
>
> Hi gophers,
>
> I hope someone can help finding out why a particular goroutine call can block
> the main
Hi gophers,
I hope someone can help finding out why a particular goroutine call can
block the main goroutine.
In the following code, all "go" calls spawn off a goroutine and return as
expected, except for the last one that blocks the main goroutine.
Is this a bug, or am I missing something