-
Notifications
You must be signed in to change notification settings - Fork 13k
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
No documentation of dropping behaviour for std::fs::File #52685
Comments
(there is a sentence "Files are automatically closed when they go out of scope.", but this doesn't discuss error handling, and it does not accurately reflect the fact that a drop and going out of scope are not the same thing.) |
retep998
added
the
A-docs
Area: Documentation for any part of the project, including the compiler, standard library, and tools
label
Jul 26, 2018
Centril
added a commit
to Centril/rust
that referenced
this issue
Apr 4, 2019
…dtolnay Document std::fs::File close behavior ignoring errors Resolves rust-lang#52685
Centril
added a commit
to Centril/rust
that referenced
this issue
Apr 4, 2019
…dtolnay Document std::fs::File close behavior ignoring errors Resolves rust-lang#52685
Centril
added a commit
to Centril/rust
that referenced
this issue
Apr 4, 2019
…dtolnay Document std::fs::File close behavior ignoring errors Resolves rust-lang#52685
Centril
added a commit
to Centril/rust
that referenced
this issue
Apr 4, 2019
…dtolnay Document std::fs::File close behavior ignoring errors Resolves rust-lang#52685
Centril
added a commit
to Centril/rust
that referenced
this issue
Apr 4, 2019
…dtolnay Document std::fs::File close behavior ignoring errors Resolves rust-lang#52685
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The dropping behaviour for
std::fs::File
is inherited through thesys::fs::File
object, meaning that its documentation does not come through to theFile
type. As a result, there is no documentation of the behaviour ofFile
and, in particular, the decision to swallow errors (likely the correct one, but it should nonetheless be documented).The text was updated successfully, but these errors were encountered: