From 92386fc65298e589d46cebd7a9e53106cb9dd6d9 Mon Sep 17 00:00:00 2001 From: oberien Date: Fri, 5 May 2017 11:28:15 +0200 Subject: [PATCH] =?UTF-8?q?Fix=20typo=20from=20`naive`=20to=20`na=C3=AFve`?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- src/ownership.md | 2 +- src/vec.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/ownership.md b/src/ownership.md index dd9e9db..2ec4872 100644 --- a/src/ownership.md +++ b/src/ownership.md @@ -59,7 +59,7 @@ data.push(4); println!("{}", x); ``` -naive scope analysis would be insufficient to prevent this bug, because `data` +naïve scope analysis would be insufficient to prevent this bug, because `data` does in fact live as long as we needed. However it was *changed* while we had a reference into it. This is why Rust requires any references to freeze the referent and its owners. diff --git a/src/vec.md b/src/vec.md index ad98e45..62580d1 100644 --- a/src/vec.md +++ b/src/vec.md @@ -13,7 +13,7 @@ many intrinsics *do* become stabilized elsewhere (`std::ptr` and `str::mem` consist of many intrinsics). Ultimately this means our implementation may not take advantage of all -possible optimizations, though it will be by no means *naive*. We will +possible optimizations, though it will be by no means *naïve*. We will definitely get into the weeds over nitty-gritty details, even when the problem doesn't *really* merit it.