Skip to content

Commit 83b9dea

Browse files
committed
Auto merge of #27459 - da-kid:master, r=steveklabnik
Sorry :/
2 parents 832e5a0 + 3dfab40 commit 83b9dea

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/doc/trpl/the-stack-and-the-heap.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ frame. But before we can show what happens when `foo()` is called, we need to
7373
visualize what’s going on with memory. Your operating system presents a view of
7474
memory to your program that’s pretty simple: a huge list of addresses, from 0
7575
to a large number, representing how much RAM your computer has. For example, if
76-
you have a gigabyte of RAM, your addresses go from `0` to `1,073,741,824`. That
76+
you have a gigabyte of RAM, your addresses go from `0` to `1,073,741,823`. That
7777
number comes from 2<sup>30</sup>, the number of bytes in a gigabyte.
7878

7979
This memory is kind of like a giant array: addresses start at zero and go
@@ -551,7 +551,7 @@ is a great introduction.
551551

552552
[wilson]: http://www.cs.northwestern.edu/~pdinda/icsclass/doc/dsa.pdf
553553

554-
## Semantic impact
554+
## Semantic impact
555555

556556
Stack-allocation impacts the Rust language itself, and thus the developer’s
557557
mental model. The LIFO semantics is what drives how the Rust language handles

0 commit comments

Comments
 (0)