tokio-rs/bytes
1
0
Fork 0
mirror of https://github.com/tokio-rs/bytes.git synced 2026-08-24 00:00:14 +02:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Phil Ruffwind
2017-04-24 12:47:24 -07:00
committed by Carl Lerche
parent e158160418
commit 0b4185c716
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/bytes.rs
+2 -2
View File
@@ -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.