The program will simply panic when you write to a closed channel, because
that kind of operations is just nonsense after the action of closing the
channel.
I afraid that the situation is similar to the nil channel operation.Because
the nil channel is not been initialized yet, so there is must be some logic
problem with the program if you w/r on a nil channel.
So the question:
Isn't it better just to throw a panic when user send/recv on a nil
channel instead of forever blocking it? If not, what is the benefits?
--
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.
