-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Doc's example code for BufferedWriter is wrong and also generate warnings #18197
Comments
So the reasons that the warnings don't happen is
They were turned off! |
steveklabnik
added a commit
to steveklabnik/rust
that referenced
this issue
Oct 28, 2014
bors
added a commit
that referenced
this issue
Oct 30, 2014
lnicola
pushed a commit
to lnicola/rust
that referenced
this issue
Oct 8, 2024
…eykril minor: Stricter requirements for package wide flycheck Require the existence of a target and `check_workspace` to be false to restart package-wide flycheck. Fixes rust-lang#18194 , rust-lang#18104
lnicola
pushed a commit
to lnicola/rust
that referenced
this issue
Dec 11, 2024
Our first attempt to make flycheck only check the current crate if the crate is one of bin/bench/test targets had caused `check_workspace` to be ignored, which should have been a config with higher precedence all along. This commit revert rust-lang#18197 and closes rust-lang#18562
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Struct std::io::BufferedWriter has the example code :
But this code opens the file as read only, it should open it for writing or creating a new file, for example :
It also generates two warnings :
by
unwrap()
ing both these remove the errors, and in the case whereFile::open
is used to successfully crash the sample app when attempting to append to a read only file.The text was updated successfully, but these errors were encountered: