From 9eda98a587bac7ff71664e2db4d97efc64c4ff1e Mon Sep 17 00:00:00 2001 From: Kevin Stock Date: Sat, 27 Feb 2016 08:26:42 -0500 Subject: [PATCH] Resolve ambiguous documentation See http://www.ietf.org/rfc/rfc2119.txt --- src/doc/book/const-and-static.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/doc/book/const-and-static.md b/src/doc/book/const-and-static.md index 7d555b52a98..b7042854bd2 100644 --- a/src/doc/book/const-and-static.md +++ b/src/doc/book/const-and-static.md @@ -64,16 +64,16 @@ unsafe { [unsafe]: unsafe.html -Furthermore, any type stored in a `static` must be `Sync`, and may not have +Furthermore, any type stored in a `static` must be `Sync`, and must not have a [`Drop`][drop] implementation. [drop]: drop.html # Initializing -Both `const` and `static` have requirements for giving them a value. They may -only be given a value that’s a constant expression. In other words, you cannot -use the result of a function call or anything similarly complex or at runtime. +Both `const` and `static` have requirements for giving them a value. They must +be given a value that’s a constant expression. In other words, you cannot use +the result of a function call or anything similarly complex or at runtime. # Which construct should I use?