about summary refs log tree commit diff
diff options
context:
space:
mode:
authorchrismit3s <chrissidtmeier@gmail.com>2021-10-01 20:07:36 +0200
committerchrismit3s <chrissidtmeier@gmail.com>2021-10-01 20:07:36 +0200
commit1a796441f5d4578923cb5dd6859dacc8c7b823d0 (patch)
treee2f5926afc58ac618777244f3a586c8bfdf9f026
parented937594d3912ced11f6f35a90bb8bf591909d2a (diff)
downloadrust-1a796441f5d4578923cb5dd6859dacc8c7b823d0.tar.gz
rust-1a796441f5d4578923cb5dd6859dacc8c7b823d0.zip
Clarify a sentence in the documentation of Vec (#84488)
-rw-r--r--library/alloc/src/vec/mod.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/library/alloc/src/vec/mod.rs b/library/alloc/src/vec/mod.rs
index c37ec375561..92b6aaadf58 100644
--- a/library/alloc/src/vec/mod.rs
+++ b/library/alloc/src/vec/mod.rs
@@ -369,7 +369,7 @@ mod spec_extend;
 /// scratch space that it may use however it wants. It will generally just do
 /// whatever is most efficient or otherwise easy to implement. Do not rely on
 /// removed data to be erased for security purposes. Even if you drop a `Vec`, its
-/// buffer may simply be reused by another `Vec`. Even if you zero a `Vec`'s memory
+/// buffer may simply be reused by another allocation. Even if you zero a `Vec`'s memory
 /// first, that might not actually happen because the optimizer does not consider
 /// this a side-effect that must be preserved. There is one case which we will
 /// not break, however: using `unsafe` code to write to the excess capacity,