-
Notifications
You must be signed in to change notification settings - Fork 13.3k
IoError is kind of archaic #16524
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
Comments
cc me |
cc me |
I may have written the FIXME, and probably I was thinking that it was 'archaic' to bubble up unixy I/O error codes with an ancient legacy and loose mapping to non-unixes. In hindsight I'm no longer too concerned about that. The names have been mostly well-rustified, and they are abstracted across platform reasonably well by virtue of the I/O stack being implemented cross-platform, and libuv already having done much of the error-unifying work for us. Another concern is that the list of possible errors is static. The naming of the variants should be scrutinized. |
Relevant: rust-lang/rfcs#201 |
This is quite an old issue and |
…r=Veykril minor: test that flip_trait_bound works with trait objects Closes rust-lang/rust-analyzer#16522.
The documentation for IoError still says
# FIXME Is something like this sufficient? It's kind of archaic
.This is an issue to track this untagged FIXME. It should be addressed or the documentation should be updated -- I'm reporting this due to a user question about IoError on IRC.
The text was updated successfully, but these errors were encountered: