News for hackers. Stuff that matters.
Re:Goroutines, Nonblocking I/O, and Memory Usage by jules on Thursday January 05, 2017 @06:20PM (#13332429)
Is this inherent in Go's concurrency model or just a limitation of the standard library? Couldn't the standard library provide a function that takes a buffer pool as an argument instead of a buffer?
Re:Goroutines, Nonblocking I/O, and Memory Usage by neild on Thursday January 05, 2017 @06:55PM (#13332635)
It's a standard library limitation.

One could imagine a function that takes a set of net.Conns and returns the ones that are available for reading. You'd then pass those off to a goroutine for processing with blocking I/O as usual.