about summary refs log tree commit diff
path: root/src/test/run-pass/thinlto
diff options
context:
space:
mode:
authorMark Simulacrum <mark.simulacrum@gmail.com>2017-07-12 06:58:48 -0600
committerGitHub <noreply@github.com>2017-07-12 06:58:48 -0600
commitcc20ab1f2509de4ef0a9953e514d62fa23b6c572 (patch)
treeba585ca57d0bd959a72679ff74f26c72181130ed /src/test/run-pass/thinlto
parent6aeb0f0b2ed6d9577f741d27e9007b7f787557fa (diff)
parentc6b280e0396780179a20776b55e3fa4cf4b1a513 (diff)
downloadrust-cc20ab1f2509de4ef0a9953e514d62fa23b6c572.tar.gz
rust-cc20ab1f2509de4ef0a9953e514d62fa23b6c572.zip
Rollup merge of #43136 - jgallag88:bufWriterDocs, r=steveklabnik
Add warning to BufWriter documentation

When using `BufWriter`, it is very easy to unintentionally ignore errors, because errors which occur when flushing buffered data when the `BufWriter` is dropped are ignored. This has been noted in a couple places:  #32677, #37045.

There has been some discussion about how to fix this problem in #32677, but no solution seems likely to land in the near future. For now, anyone who wishes to have robust error handling must remember to manually call `flush()` on a `BufWriter` before it is dropped.  Until a permanent fix is in place, it seems worthwhile to add a warning to that effect to the documentation.
Diffstat (limited to 'src/test/run-pass/thinlto')
0 files changed, 0 insertions, 0 deletions