Skip to content
Snippets Groups Projects
Commit 0b4185c7 authored by Phil Ruffwind's avatar Phil Ruffwind Committed by Carl Lerche
Browse files

Fix typos in src/bytes.rs (#106)

parent e1581604
No related branches found
No related tags found
No related merge requests found
...@@ -87,13 +87,13 @@ use std::sync::atomic::Ordering::{Relaxed, Acquire, Release, AcqRel}; ...@@ -87,13 +87,13 @@ use std::sync::atomic::Ordering::{Relaxed, Acquire, Release, AcqRel};
/// underlying memory slice and may not be mutated, `BytesMut` handles are /// underlying memory slice and may not be mutated, `BytesMut` handles are
/// guaranteed to be the only handle able to view that slice of memory. As such, /// guaranteed to be the only handle able to view that slice of memory. As such,
/// `BytesMut` handles are able to mutate the underlying memory. Note that /// `BytesMut` handles are able to mutate the underlying memory. Note that
/// holding a unique view to a region of memory does not mean that there are not /// holding a unique view to a region of memory does not mean that there are no
/// other `Bytes` and `BytesMut` handles with disjoint views of the underlying /// other `Bytes` and `BytesMut` handles with disjoint views of the underlying
/// memory. /// memory.
/// ///
/// # Inline bytes. /// # Inline bytes.
/// ///
/// As an opitmization, when the slice referenced by a `Bytes` or `BytesMut` /// As an optimization, when the slice referenced by a `Bytes` or `BytesMut`
/// handle is small enough [1], `Bytes` will avoid the allocation by inlining /// handle is small enough [1], `Bytes` will avoid the allocation by inlining
/// the slice directly in the handle. In this case, a clone is no longer /// the slice directly in the handle. In this case, a clone is no longer
/// "shallow" and the data will be copied. /// "shallow" and the data will be copied.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment