News for hackers. Stuff that matters.
Re:Goroutines, Nonblocking I/O, and Memory Usage by zzzcpan on Thursday January 05, 2017 @05:12PM (#13331911)
No, it checks for zero-length buffers and returns immediately. You would have to read at least a byte and copy it into a new buffer.

Won't matter much though, as the memory usage of a single goroutine is quite significant and doubling it by having a buffer preallocated is not something to care about.

Re:Goroutines, Nonblocking I/O, and Memory Usage by masklinn on Thursday January 05, 2017 @05:24PM (#13332013)
> Won't matter much though, as the memory usage of a single goroutine is quite significant

2K as of 1.4 (was 4K before 1.2, 8K in 1.2 and 1.3).

But yeah it's a good point, the intrinsic memory overhead of goroutines means even if buffer pooling worked the memory use of the system would still mostly follow the "naive" estimate.

You may want to message the author to remind them of that, they may not have thought of that concern.