> it's good to have blocking and non-blocking channel reads.
That's not really his issue. His issue seems to be the overloading of the channel read to very different operations based on the number of return values.
I don't think he'd have minded if blocking and non-blocking channel reads were different operators, but it's the same operator returning either one or two values. It's harder to read.
That's not really his issue. His issue seems to be the overloading of the channel read to very different operations based on the number of return values.
I don't think he'd have minded if blocking and non-blocking channel reads were different operators, but it's the same operator returning either one or two values. It's harder to read.