why the task channel of the workers not be closed

[yugu2day]

I found that when purging/resetting the workers, simply setting it to nil and sending nil to the task channel so that it can stop the for range loop in the worker's run function.

func (wq *workerStack) reset() {
	for i := 0; i < wq.len(); i++ {
		wq.items[i].finish()
		wq.items[i] = nil
	}
	wq.items = wq.items[:0]
}

However, the task channel remains open although it can be garbage collected finally. But why don't we close it directly?

[panjf2000]

Like you said, there wouldn't be any memory leaks, so why should we bother to close it? I don't see any obligated instructions about closing the used channels in the Go specification and effective Go. Generally speaking, we need a reason to do something more than a reason not to do something.

[yugu2day]

got it, thanks for your explanation.