Re: [go-nuts] Channel receive operator. Untyped boolean result.

2020-06-22 Thread Laevus Dexter
I get it, thanks. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://grou

[go-nuts] Channel receive operator. Untyped boolean result.

2020-06-21 Thread Laevus Dexter
> > A receive expression used in an assignment > or initialization of the > special form > > x, ok = <-ch > x, ok := <-ch > var x, ok = <-ch > var x, ok T = <-ch > > yields an additional untyped boolean result reporting whether the > communication succe

Re: [go-nuts] asmcgocall and async preemption

2020-03-29 Thread Laevus Dexter
I see, thank you. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://grou

[go-nuts] asmcgocall and async preemption

2020-03-29 Thread Laevus Dexter
Go 1.14 has introduced new async preemption stuff. I'm wondering what would happen if you were inside C code and preemption signal has arrived? How can I reproduce this case to test stuff like this: https://github.com/LaevusDexter/asmcgocall ? -- You received this message because you are subsc