Applied some spellchecker suggestions

This commit is contained in:
Yuri Astrakhan
2024-07-16 15:59:45 -04:00
parent eebbbb0086
commit c32d7a79a2
17 changed files with 44 additions and 44 deletions

View File

@@ -50,7 +50,7 @@
//! Using `MaybeUninit` here can be more efficient in some cases, but is
//! often inconvenient, so both are provided.
//!
//! 2. Exact/inexact refers to to whether or not the entire buffer must be
//! 2. Exact/inexact refers to whether or not the entire buffer must be
//! filled in order for the call to be considered a success.
//!
//! The "exact" functions require the provided buffer be entirely filled, or
@@ -287,7 +287,7 @@ impl Blob<'_> {
/// Close a BLOB handle.
///
/// Calling `close` explicitly is not required (the BLOB will be closed
/// when the `Blob` is dropped), but it is available so you can get any
/// when the `Blob` is dropped), but it is available, so you can get any
/// errors that occur.
///
/// # Failure

View File

@@ -116,7 +116,7 @@ impl<'conn> Blob<'conn> {
if read_len == 0 {
// We could return `Ok(&mut [])`, but it seems confusing that the
// pointers don't match, so fabricate a empty slice of u8 with the
// pointers don't match, so fabricate an empty slice of u8 with the
// same base pointer as `buf`.
let empty = unsafe { from_raw_parts_mut(buf.as_mut_ptr().cast::<u8>(), 0) };
return Ok(empty);