Thanks, Ja kub, for the enthusiasm. :) Thanks, Ian, for the background.
Ja kub: If it helps, I never close channels that are sent on. I recommend this approach. Once one adopts this approach, then the rationale for double close being a panic disappears. The irony is not lost on me that Ian's, "somehow coordinate that there is nothing else to send" is the purpose for which I invaraibly deploy idempotent close. I use it for cancellation, erroring out, bailing out, and sub-system or full-system shutdown. (Close is the only broadcast primitive available that plays well with select, and thus with timeouts.) Pont also liberates close() from its 1-bit straight-jacket, as Pont can broadcast pointers or any value. :) Cheers, Jason -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/a636bdc8-46af-4110-832c-98d86a008ce8n%40googlegroups.com.
