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.
This commit is contained in:
parent
894f7a4ba6
commit
09006d6a88
9 changed files with 32 additions and 26 deletions
|
@ -1,13 +1,14 @@
|
|||
///! An encapsulation of `BufReader`'s buffer management logic.
|
||||
///
|
||||
/// This module factors out the basic functionality of `BufReader` in order to protect two core
|
||||
/// invariants:
|
||||
/// * `filled` bytes of `buf` are always initialized
|
||||
/// * `pos` is always <= `filled`
|
||||
/// Since this module encapsulates the buffer management logic, we can ensure that the range
|
||||
/// `pos..filled` is always a valid index into the initialized region of the buffer. This means
|
||||
/// that user code which wants to do reads from a `BufReader` via `buffer` + `consume` can do so
|
||||
/// without encountering any runtime bounds checks.
|
||||
//! An encapsulation of `BufReader`'s buffer management logic.
|
||||
//!
|
||||
//! This module factors out the basic functionality of `BufReader` in order to protect two core
|
||||
//! invariants:
|
||||
//! * `filled` bytes of `buf` are always initialized
|
||||
//! * `pos` is always <= `filled`
|
||||
//! Since this module encapsulates the buffer management logic, we can ensure that the range
|
||||
//! `pos..filled` is always a valid index into the initialized region of the buffer. This means
|
||||
//! that user code which wants to do reads from a `BufReader` via `buffer` + `consume` can do so
|
||||
//! without encountering any runtime bounds checks.
|
||||
|
||||
use crate::cmp;
|
||||
use crate::io::{self, BorrowedBuf, Read};
|
||||
use crate::mem::MaybeUninit;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue