Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

os, syscall: changes to os.Err* and syscall.Errno not mentioned in release notes and syscall package docs #33436

Closed
bcmills opened this issue Aug 2, 2019 · 2 comments

Comments

@bcmills
Copy link
Member

commented Aug 2, 2019

The changes made to the os and syscall package for #30322 are not mentioned in the Go 1.13 release notes, nor in the documentation for syscall.Errno or the syscall package.

Because users in general cannot redefine the error behavior of the errors defined by their dependencies, as a user I would not expect syscall.Errno errors to be defined as equivalent to errors defined in the higher-level os package. As noted in #32463 and #33411, the fact that they are has significant, non-trivial implications.

If errors.Is is now recommended and supported for checking the properties of syscall.Errno errors, the syscall.Errno documentation and the Go 1.13 release notes should be updated to mention that.

CC @neild @jba @mpvl @rsc @andybons @ianlancetaylor

@ianlancetaylor

This comment has been minimized.

Copy link
Contributor

commented Aug 21, 2019

Ping @jba Want to write something about this as you've written other error-related docs?

@gopherbot

This comment has been minimized.

Copy link

commented Aug 22, 2019

Change https://golang.org/cl/191337 mentions this issue: syscall: document relationship among Errno, errors.Is and os.Err*

@gopherbot gopherbot closed this in 65e624e Aug 22, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.