From adcd30c5a2aa732174b0c5deba3f4b9c9a9a44d0 Mon Sep 17 00:00:00 2001 From: Alexis Beingessner Date: Mon, 6 Jul 2015 20:28:11 -0700 Subject: [PATCH] mdinger fix --- safe-unsafe-meaning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/safe-unsafe-meaning.md b/safe-unsafe-meaning.md index 8a6300a061d2..6c3d4087b819 100644 --- a/safe-unsafe-meaning.md +++ b/safe-unsafe-meaning.md @@ -98,7 +98,7 @@ destructors will be successfully called! Hooray! However BTreeMap is implemented using a modest spoonful of Unsafe (most collections are). That means that it is not necessarily *trivially true* that a bad Ord -implementation will make BTreeMap behave safely. Unsafe most be sure not to rely +implementation will make BTreeMap behave safely. Unsafe must be sure not to rely on Ord *where safety is at stake*, because Ord is provided by Safe, and memory safety is not Safe's responsibility to uphold. *It must be impossible for Safe code to violate memory safety*.