diff options
| author | Steve Klabnik <steve@steveklabnik.com> | 2015-11-06 17:42:53 +0100 |
|---|---|---|
| committer | Steve Klabnik <steve@steveklabnik.com> | 2015-11-06 17:44:04 +0100 |
| commit | 5eacf66c48db342b0e1056531307dbe318d9f16d (patch) | |
| tree | 5ac5b50c630d412456f89eca382b65d3a1b35591 | |
| parent | a216e847272ddbd3033037b606eaf2d801c250b9 (diff) | |
| download | rust-5eacf66c48db342b0e1056531307dbe318d9f16d.tar.gz rust-5eacf66c48db342b0e1056531307dbe318d9f16d.zip | |
Make a note about "gigabyte"
Fixes #28461
| -rw-r--r-- | src/doc/trpl/the-stack-and-the-heap.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/src/doc/trpl/the-stack-and-the-heap.md b/src/doc/trpl/the-stack-and-the-heap.md index 0bc2ca263d5..f835322ee71 100644 --- a/src/doc/trpl/the-stack-and-the-heap.md +++ b/src/doc/trpl/the-stack-and-the-heap.md @@ -74,7 +74,9 @@ visualize what’s going on with memory. Your operating system presents a view o 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,823`. That -number comes from 2<sup>30</sup>, the number of bytes in a gigabyte. +number comes from 2<sup>30</sup>, the number of bytes in a gigabyte. [^gigabyte] + +[^gigabyte]: ‘Gigabyte’ can mean two things: 10^9, or 2^30. The SI standard resolved this by stating that ‘gigabyte’ is 10^9, and ‘gibibyte’ is 2^30. However, very few people use this terminology, and rely on context to differentiate. We follow in that tradition here. This memory is kind of like a giant array: addresses start at zero and go up to the final number. So here’s a diagram of our first stack frame: |
