joboet
c14d137bfc
std: update internal uses of io::const_error!
2024-11-26 18:38:24 +01:00
Matthias Krüger
6e9db86787
Rollup merge of #125404 - a1phyr:fix-read_buf-uses, r=workingjubilee
...
Fix `read_buf` uses in `std`
Following lib-team decision here: https://github.com/rust-lang/rust/issues/78485#issuecomment-2122992314
Guard against the pathological behavior of both returning an error and performing a read.
2024-09-28 09:35:08 +02:00
Josh Stone
1e9a50dde8
Pre-allocate buffers in File::open_buffered
and create_buffered
2024-09-24 13:33:31 -07:00
Benoît du Garreau
04710e27d2
Fix io::BufReader
uses of read_buf
2024-09-23 22:51:27 +02:00
binarycat
dfdbf6343a
properly handle EOF in BufReader::peek
...
previously this would cause an infinite loop due to it being
unable to read `n` bytes.
2024-09-06 16:28:22 -04:00
binarycat
4af77dfea5
implement BufReader::peek
2024-08-05 15:44:54 -04:00
Nicholas Nethercote
09006d6a88
Convert some module-level //
and ///
comments to //!
.
...
This makes their intent and expected location clearer. We see some
examples where these comments were not clearly separate from `use`
declarations, which made it hard to understand what the comment is
describing.
2024-06-20 09:23:18 +10:00
Ben Kimock
95ae993bd8
Avoid defensive re-initialization of the BufReader buffer
2022-10-06 23:31:57 -04:00
Nick Cameron
ac70aea985
Address reviewer comments
...
Signed-off-by: Nick Cameron <nrc@ncameron.org>
2022-08-18 10:34:40 +01:00
Nick Cameron
1a2122fff0
non-linux platforms
...
Signed-off-by: Nick Cameron <nrc@ncameron.org>
2022-08-05 17:18:51 +01:00
Ben Kimock
5fa1926634
Add Buffer::consume_with to enable direct buffer access with one check
2022-07-26 20:16:55 -04:00
Ben Kimock
5e5ce4327a
Rename and document the new BufReader internals
2022-07-24 13:51:09 -04:00
Ben Kimock
b9497be7d0
Allow Buffer methods to inline
2022-07-24 12:50:05 -04:00
Ben Kimock
761ddf3e7f
Remove some redundant checks from BufReader
...
The implementation of BufReader contains a lot of redundant checks.
While any one of these checks is not particularly expensive to execute,
especially when taken together they dramatically inhibit LLVM's ability
to make subsequent optimizations.
2022-07-24 12:50:05 -04:00