diff options
| author | Pietro Albini <pietro@pietroalbini.org> | 2018-07-03 11:30:59 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-07-03 11:30:59 +0200 |
| commit | a3fc979b6bf29edf02fe7f9930ca99c8e2d5d84c (patch) | |
| tree | e26a80eddd5fb6abc64d23a7b0411071e52ef556 /src/test/incremental/thinlto | |
| parent | 7fa03fb511a0ee8c5abbe2e3ea545d0df02f5e41 (diff) | |
| parent | 73166f751b7509dd95ce903ecdeab2dd5d89aa90 (diff) | |
| download | rust-a3fc979b6bf29edf02fe7f9930ca99c8e2d5d84c.tar.gz rust-a3fc979b6bf29edf02fe7f9930ca99c8e2d5d84c.zip | |
Rollup merge of #51809 - drrlvn:rw_exact_all_at, r=alexcrichton
Add read_exact_at and write_all_at methods to FileExt on unix This PR adds `FileExt::read_exact_at()` and `FileExt::write_all_at()`, which are to `read_at()` and `write_at()` as `read_exact()` and `write_all()` are to `read()` and `write()`. This allows the user to not have to deal with `ErrorKind::Interrupted` and calling the functions in a loop. I was unsure as to how to mark these new methods so I marked them `unstable`, please let me know if I should have done it differently. I asked in Discord and was told that as this change is small it does not require an RFC.
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions