Does go programmers should handle syscall.EINTR all by themselves after 
go1.9 when writing disk files?

I just noticed this commit 
https://github.com/golang/go/commit/c05b06a12d005f50e4776095a60d6bd9c2c91fac#diff-b7452e0f27c15f140b5e86f88e2d43deL192

If the answer is 'yes', I wonder why deleted this loop-write-if-eintr 
logic? Does it not bring unnecessary inconvenience to the go programmer?

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to