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

std::io: new ErrorKind value InvalidParam #25406

Closed
wants to merge 1 commit into from

Conversation

mzabaluev
Copy link
Contributor

Resolves rust-lang/rfcs#906.

This is an alternative to #25246, done at the suggestion by @bluss that preserving the InvalidInput error code in cases where invalid external data may be involved is better for minimizing impact of the change.

This takes over usages of InvalidInput where invalid parameter use
likely arises from a program error. InvalidInput is dedicated to
occurrences of invalid or malformed data in I/O, which may or may
not be caused by deficient programming.
@rust-highfive
Copy link
Collaborator

r? @nikomatsakis

(rust_highfive has picked a reviewer for you, use r? to override)

@mzabaluev
Copy link
Contributor Author

Cc @alexcrichton, @aturon.

@aturon
Copy link
Member

aturon commented May 14, 2015

I prefer #25246, which I think gets at a more clear distinction.

@alexcrichton
Copy link
Member

I also agree with @aturon that I'd prefer #25246

@nikomatsakis
Copy link
Contributor

Per the comments from @alexcrichton and @aturon, I am closing this PR in favor of #25246, feel free to re-open if you disagree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Ambiguous usage of std::io::ErrorKind::InvalidInput
5 participants