diff options
| author | Yuki Okushi <huyuumi.dev@gmail.com> | 2019-11-08 13:42:12 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-11-08 13:42:12 +0900 |
| commit | 32aa327ba35c4b0f95c7c4cd983f1867fc498897 (patch) | |
| tree | 67cd0ea353e5a27d99c7249f93c9d49d93081b32 /src/test/debuginfo/enum-thinlto.rs | |
| parent | d2574403b31508be9cfed468e352467043d2354d (diff) | |
| parent | 5b5196ad65db877c2f140dfc7a25f3fc6f2e40c6 (diff) | |
| download | rust-32aa327ba35c4b0f95c7c4cd983f1867fc498897.tar.gz rust-32aa327ba35c4b0f95c7c4cd983f1867fc498897.zip | |
Rollup merge of #65554 - gliderkite:bufreader-doc-enhance, r=KodrAus
Enhance the documentation of BufReader for potential data loss This is (IMO) and enhancement of the `std::io::BufReader` documentation, that aims to highlight how relatively easy is to end up with data loss when improperly using an instance of this class. This is following the issue I had figuring out why my application was loosing data, because I focused my attention on the word *multiple instances* of `BufReader` in its `struct` documentation, even if I ever only had one instance. Link to the issue: https://github.com/tokio-rs/tokio/issues/1662
Diffstat (limited to 'src/test/debuginfo/enum-thinlto.rs')
0 files changed, 0 insertions, 0 deletions