Au contraire: Go has a built-in 'select' keyword that lets you wait on a set of ...

neilc · on Jan 18, 2017

Channels are not network sockets; select cannot be used to wait on a set of network sockets.

(Early versions of Go had a "network channel" concept, but that was removed from the language: https://softwareengineering.stackexchange.com/questions/1540...)

atombender · on Jan 18, 2017

select{} has nothing to with select(), epoll etc. It works on channels only, which are not implemented using those syscalls.

Groxx · on Jan 18, 2017

A goroutine is a "task" though. And typically you spin up a goroutine for your select, and hang your current goroutine on its completion.

Seems pretty similar to me.

azernik · on Jan 19, 2017

For networking, it's using epoll() under the scenes; depends on what exact non-blocking operation you're using, though.

See this very very old HN thread:

(Hopefully the standard library has improved since then.)

coldtea · on Jan 18, 2017

That's not access to the raw system's select/epoll.

It just happens to offer a similar model (and have a select operation).