Re:Threads Are a Bad Idea for Most Purposes (1995) [pdf]
by loopz on Thursday January 30, 2020 @04:12PM
(#22195660)
Such things bites everyone. But writing to closed channel is regarded as programming error. You potentially lose values. So logic should be watertight, which is hard with concurrency. Doing simplest approach to locking helps.
Better with panic than silent errors and flawed logic.
It's just that there exist ways to shoot yourself in the foot quite easily.
Example: I'd find it much more intuitive if writing to a closed channel returned an error value and didn't issue a panic.
But I'm guessing that the Go programmers get used to the assumptions that must be made when working with the language so such things are likely quite fine with them and cause them no grief.