diff options
| author | Alexander Regueiro <alexreg@me.com> | 2019-09-05 17:15:28 +0100 |
|---|---|---|
| committer | Alexander Regueiro <alexreg@me.com> | 2019-09-06 16:02:25 +0100 |
| commit | b0006dff1041f0eea718ca29607cd6ec372e4e30 (patch) | |
| tree | de6d8a0d438052c300a561078082bb1f2d62c203 /src/liballoc/raw_vec | |
| parent | 1fb3c4ec7ca37d33bd1e68cce669d171c2752615 (diff) | |
| download | rust-b0006dff1041f0eea718ca29607cd6ec372e4e30.tar.gz rust-b0006dff1041f0eea718ca29607cd6ec372e4e30.zip | |
A few cosmetic improvements to code & comments in liballoc and libcore
Diffstat (limited to 'src/liballoc/raw_vec')
| -rw-r--r-- | src/liballoc/raw_vec/tests.rs | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/liballoc/raw_vec/tests.rs b/src/liballoc/raw_vec/tests.rs index c389898d1ef..d35b62fc1ef 100644 --- a/src/liballoc/raw_vec/tests.rs +++ b/src/liballoc/raw_vec/tests.rs @@ -5,12 +5,12 @@ fn allocator_param() { use crate::alloc::AllocErr; // Writing a test of integration between third-party - // allocators and RawVec is a little tricky because the RawVec + // allocators and `RawVec` is a little tricky because the `RawVec` // API does not expose fallible allocation methods, so we // cannot check what happens when allocator is exhausted // (beyond detecting a panic). // - // Instead, this just checks that the RawVec methods do at + // Instead, this just checks that the `RawVec` methods do at // least go through the Allocator API when it reserves // storage. @@ -44,7 +44,7 @@ fn allocator_param() { fn reserve_does_not_overallocate() { { let mut v: RawVec<u32> = RawVec::new(); - // First `reserve` allocates like `reserve_exact` + // First, `reserve` allocates like `reserve_exact`. v.reserve(0, 9); assert_eq!(9, v.capacity()); } |
