Josh Triplett 382509988b Remove initialized-bytes tracking from BorrowedBuf and BorrowedCursor ...

As discussed extensively in libs-api, the initialized-bytes tracking
primarily benefits calls to `read_buf` that end up initializing the
buffer and calling `read`, at the expense of calls to `read_buf` that
*don't* need to initialize the buffer. Essentially, this optimizes for
the past at the expense of the future. If people observe performance
issues using `read_buf` (or something that calls it) with a given `Read`
impl, they can fix those performance issues by implementing `read_buf`
for that `Read`.

Update the documentation to stop talking about initialized-but-unfilled
bytes.

Remove all functions that just deal with those bytes and their tracking,
and remove usage of those methods.

Remove `BorrowedCursor::advance` as there's no longer a safe case for
advancing within initialized-but-unfilled bytes. Rename
`BorrowedCursor::advance_unchecked` to `advance`.

Update tests.

2025-12-02 01:32:27 -08:00

..

borrowed_buf.rs

Remove initialized-bytes tracking from BorrowedBuf and BorrowedCursor

2025-12-02 01:32:27 -08:00

mod.rs

Put all coretests in a separate crate

2025-01-26 10:26:36 +00:00