News for hackers. Stuff that matters.
Re:Goroutines, Nonblocking I/O, and Memory Usage by eternalban on Thursday January 05, 2017 @07:31PM (#13332847)
> there is literally no way to poll a file descriptor

https://godoc.org/golang.org/x/sys

https://godoc.org/golang.org/x/sys/unix#EpollWait

https://golang.org/pkg/syscall/

Of course it is a bit of a pain to write OS specific variants if you are building a completely crossplatform solution, but it is supported out of the box:

https://dave.cheney.net/2013/10/12/how-to-use-conditional-co...

That said, I agree [regarding the] puzzling decision to not to treat 'select' as a general contract for all asynchronous ops as that fits perfectly with the CSP approach.

Re:Goroutines, Nonblocking I/O, and Memory Usage by lobster_johnson on Thursday January 05, 2017 @08:42PM (#13333237)
Indeed, though I was referring to select{}, i.e. Go's first-class language constructs.