Concurrency made easy - GopherCon SG 2017

[@wangfenjin]

For why close the error channel: Because if you don't close the error channel, the last return statement maybe blocked forever if there is no value in the chan. Receive from a closed chan will return immediately even if it's empty.

[@FrenchPirate83]

Minor, but could sem not have been a chan struct{} instead of a chan int?

[@able2663]

nice sharing.

[@remariorichards8237]

hi, why did you not close the error channel as well?

[@niharrathod]

Same question. Any idea why?

[@wangfenjin]

Because if you don't close the error channel, the last return statement maybe blocked forever if there is no value in the chan. Receive from a closed chan will return immediately even if it's empty.

[@niharrathod]

Thanks Fengin

[@mikei4min]

By the way Dave Cheney is a great author - dave.cheney.net/!

[@欧阳楚-h4e]

fatal error: all goroutines are asleep - deadlock!

[@老撒-m7b]

i think it's OK if not close errchan