1
Fork 0

chore: remove redundant words in comment

Signed-off-by: crystalstall <crystalruby@qq.com>
This commit is contained in:
crystalstall 2025-01-06 15:47:49 +08:00
parent 56f9e6f935
commit 591bf63439
5 changed files with 5 additions and 5 deletions

View file

@ -550,7 +550,7 @@ impl OsString {
OsStr::from_inner_mut(self.inner.leak())
}
/// Truncate the the `OsString` to the specified length.
/// Truncate the `OsString` to the specified length.
///
/// # Panics
/// Panics if `len` does not lie on a valid `OsStr` boundary

View file

@ -97,7 +97,7 @@ impl PipeReader {
/// let mut jobs = vec![];
/// let (reader, mut writer) = std::pipe::pipe()?;
///
/// // Write NUM_SLOT characters the the pipe.
/// // Write NUM_SLOT characters the pipe.
/// writer.write_all(&[b'|'; NUM_SLOT as usize])?;
///
/// // Spawn several processes that read a character from the pipe, do some work, then

View file

@ -534,7 +534,7 @@ impl<T: ?Sized> Mutex<T> {
/// # Errors
///
/// If another user of this mutex panicked while holding the mutex, then
/// this call will return an error containing the the underlying data
/// this call will return an error containing the underlying data
/// instead.
///
/// # Examples

View file

@ -10,7 +10,7 @@ https://sourceware.org/bugzilla/show_bug.cgi?id=28509
And this is the first version of the proposed binutils patch,
https://sourceware.org/pipermail/binutils/2021-November/118398.html
After applying the binutils patch, I get the the unexpected error when
After applying the binutils patch, I get the unexpected error when
building libgcc,
/scratch/nelsonc/riscv-gnu-toolchain/riscv-gcc/libgcc/config/riscv/div.S:42:

View file

@ -1,5 +1,5 @@
// Here, there are two types with the same name. One of these has a `derive` annotation, but in the
// expansion these `impl`s are associated to the the *other* type. There is a suggestion to remove
// expansion these `impl`s are associated to the *other* type. There is a suggestion to remove
// unneeded type parameters, but because we're now point at a type with no type parameters, the
// suggestion would suggest removing code from an empty span, which would ICE in nightly.
//