From 9d2c45d0e7c18542a0abbcc4ac582cc7dbe8b060 Mon Sep 17 00:00:00 2001 From: Brian Green Date: Mon, 9 May 2016 14:28:42 -0700 Subject: [PATCH] doc: Fix tiny typo in vec-alloc.md Change `fast an loose` to `fast and loose`. --- src/doc/nomicon/vec-alloc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/doc/nomicon/vec-alloc.md b/src/doc/nomicon/vec-alloc.md index c2ae1a4eb6d26..bc60a577bd35c 100644 --- a/src/doc/nomicon/vec-alloc.md +++ b/src/doc/nomicon/vec-alloc.md @@ -150,7 +150,7 @@ LLVM needs to work with different languages' semantics and custom allocators, it can't really intimately understand allocation. Instead, the main idea behind allocation is "doesn't overlap with other stuff". That is, heap allocations, stack allocations, and globals don't randomly overlap. Yep, it's about alias -analysis. As such, Rust can technically play a bit fast an loose with the notion of +analysis. As such, Rust can technically play a bit fast and loose with the notion of an allocation as long as it's *consistent*. Getting back to the empty allocation case, there are a couple of places where