-
Notifications
You must be signed in to change notification settings - Fork 677
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
Stop reexporting Errno
variants
#696
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This also needs a changelog entry under "Removed" that states that the errno constants were removed from a specific path.
} | ||
|
||
/// Create a new invalid argument error (`EINVAL`) | ||
pub fn invalid_argument() -> Error { | ||
Error::Sys(errno::EINVAL) | ||
Error::Sys(Errno::EINVAL) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not certain that I like Errno::EINVAL
and Errno::last()
. I don't think it makes sense for last()
to be in the same place in the heirarchy as EINVAL
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure about that? This is definitely the most "rustic" way to do it.
This still actually has Errno visible from the root when I think it should stay within |
LGTM. @asomers You want to give this a lookover at all? |
@jonas-schievink if you could squash this into a single commit, I'll go ahead and merge this. Thanks! |
cc #664 (unsure if this is everything needed)
Perfect, thanks @jonas-schievink! bors r+ |
Closes #664 (unsure if this is everything needed)