News for hackers. Stuff that matters.
Re:Goroutines, Nonblocking I/O, and Memory Usage by Matthias247 on Thursday January 05, 2017 @05:38PM (#13332104)
Have never tried it with Go and don't know that the contract is there, but the approach in general is valid. Afaik you can use it with Windows IOCP to avoid the occupied buffer problem: Start an async read with a zero byte buffer and when you get the completion notificaton issue a non-blocking read with the then allocated target buffer.

There are no comments on this comment yet.