tree 9e5b7586d8502acc69df04ffed23e16542b8916f
parent 9060382bd4573352ac5bd6af10f02c31001a8786
author Tobias Klauser <tklauser@distanz.ch> 1614100294 +0100
committer Tobias Klauser <tobias.klauser@gmail.com> 1614154822 +0000

internal/socket: check for EWOULDBLOCK on all platforms

Don't make the check for EWOULDBLOCK zos-specific. Most platforms define
EAGAIN and EWOULDBLOCK with the same underlying value. Thus, the
additional check will be a no-op on them. On platforms where EAGAIN and
EWOULDBLOCK have different underlying values, we probably want to check
both as well.

As pointed out by Michael Munday in CL 264028.

Change-Id: Id3404fc4440c66a3484975b4c94b4ebb788b80a1
Reviewed-on: https://go-review.googlesource.com/c/net/+/295569
Trust: Tobias Klauser <tobias.klauser@gmail.com>
Run-TryBot: Tobias Klauser <tobias.klauser@gmail.com>
Reviewed-by: Ian Lance Taylor <iant@golang.org>