It would be much more odd, imho, for a select case to be chosen because a send can proceed, and for it then to block while generating the value to send. Simple politeness mandates that we have a value ready and evaluated when it becomes time to send it.
//jb On 31 Dec 2017, at 16:41, dc0d <kaveh.shahbaz...@gmail.com<mailto:kaveh.shahbaz...@gmail.com>> wrote: Or the (not only) other option is check for nil channels before entering the scope of select? -- 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<mailto:golang-nuts+unsubscr...@googlegroups.com>. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
