in #golang the number one noob error is using goroutines without thinking about how they are going to terminate
just removed ANOTHER goroutine and bugs disappeared
le sigh
Discussion
Reading the Kernighan book on Go right now. Looking forward to getting to the fun stuff.
oh, please, please don't become a goroutine abuser... always plan how the goroutine is gonna end before you slap yet another go statement into your code
it's one of the most irritating things and sorry not sorry but i know a person hasn't been writing code in #golang for more than a couple years when i find this kind of shit, and debugging poorly thought out concurrency is almost the literal hell