> If you do this in Go, you should use golang.org/x/sys/unix package
> rather than the syscall package.
What's the advantage? (In this particular case, not in general.)
> But since you have to call C anyhow, I would suggest just doing it in C.
Yeah, I guess it's simpler.
> There isn't any way to hook into Go's scheduler for this. Go's
> scheduler provides no mechanism for waiting for data without reading
> the data.
I suppose it makes sense, the operation might be difficult to implement in
a hypothetical scheduler that's layered over mainframe-style async operations.
Thanks for your reply,
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.