Fix off-by-one error
This commit is contained in:
parent
832e5a02cd
commit
3dfab40bbc
|
@ -73,7 +73,7 @@ frame. But before we can show what happens when `foo()` is called, we need to
|
|||
visualize what’s going on with memory. Your operating system presents a view of
|
||||
memory to your program that’s pretty simple: a huge list of addresses, from 0
|
||||
to a large number, representing how much RAM your computer has. For example, if
|
||||
you have a gigabyte of RAM, your addresses go from `0` to `1,073,741,824`. That
|
||||
you have a gigabyte of RAM, your addresses go from `0` to `1,073,741,823`. That
|
||||
number comes from 2<sup>30</sup>, the number of bytes in a gigabyte.
|
||||
|
||||
This memory is kind of like a giant array: addresses start at zero and go
|
||||
|
@ -551,7 +551,7 @@ is a great introduction.
|
|||
|
||||
[wilson]: http://www.cs.northwestern.edu/~pdinda/icsclass/doc/dsa.pdf
|
||||
|
||||
## Semantic impact
|
||||
## Semantic impact
|
||||
|
||||
Stack-allocation impacts the Rust language itself, and thus the developer’s
|
||||
mental model. The LIFO semantics is what drives how the Rust language handles
|
||||
|
|
Loading…
Reference in New Issue