From cf36a0f9c0523acb0351c14a6dd6e7ad88e06466 Mon Sep 17 00:00:00 2001 From: Christian Vallentin Date: Fri, 31 Jan 2020 16:54:41 +0100 Subject: [PATCH] Removed repeated word --- src/vec-alloc.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/vec-alloc.md b/src/vec-alloc.md index 2889a73..694059d 100644 --- a/src/vec-alloc.md +++ b/src/vec-alloc.md @@ -37,7 +37,7 @@ that, we'll need to use the rest of the heap APIs. These basically allow us to talk directly to Rust's allocator (jemalloc by default). We'll also need a way to handle out-of-memory (OOM) conditions. The standard -library calls `std::alloc::oom()`, which in turn calls the the `oom` langitem, +library calls `std::alloc::oom()`, which in turn calls the `oom` langitem, which aborts the program in a platform-specific manner. The reason we abort and don't panic is because unwinding can cause allocations to happen, and that seems like a bad thing to do when your allocator just came