From b2779ce70c5c927e3a197740e9bc05145afb1895 Mon Sep 17 00:00:00 2001 From: Bradlee Speice Date: Tue, 15 Jan 2019 22:54:21 -0500 Subject: [PATCH] Minor tweaks --- _drafts/understanding-allocations-in-rust.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_drafts/understanding-allocations-in-rust.md b/_drafts/understanding-allocations-in-rust.md index d8613e0..ea55da9 100644 --- a/_drafts/understanding-allocations-in-rust.md +++ b/_drafts/understanding-allocations-in-rust.md @@ -121,7 +121,7 @@ variables because we know exactly how much space is needed. The `eax` register is re-used to store the final result. 2. Because `MICROS_PER_MILLI` and `NANOS_PER_MICRO` are constants, the compiler never allocates memory, and just burns the constants into the final program. - - Look for the `mov edi, 1000` and `mov ecx, 1000`. + - Look for the instructions `mov edi, 1000` and `mov ecx, 1000`. Given this information, the compiler can efficiently lay out your memory usage so that the program never needs to ask the kernel/allocator for memory! This example