Nothing is known beforehand indeed. That does not mean it's not possible to expect a certain semantic for a certain syntax beforehand.
On Sunday, December 31, 2017 at 9:36:37 PM UTC+3:30, leaf...@gmail.com wrote: > > > How putting one channel inside the parameters has not any effect on the > logic of that select statement. > > True. > > My point is, whether a channel is nil or not is often not known to the > coder, and this whether the first will be called or not is unknown. Pass > the channel as a parameter emphasize how the behavior change by a parameter > to a certain value (nil). It is against your argument. > > I would say common sense is, no matter what value is sent as param, the > code has same logic, not having to keep it in mind that I have to test if > the channel is nil and write other code. > > -- 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.
