summaryrefslogtreecommitdiffstats
path: root/src/doc/book/redirects/the-stack-and-the-heap.md
diff options
context:
space:
mode:
Diffstat (limited to 'src/doc/book/redirects/the-stack-and-the-heap.md')
-rw-r--r--src/doc/book/redirects/the-stack-and-the-heap.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/src/doc/book/redirects/the-stack-and-the-heap.md b/src/doc/book/redirects/the-stack-and-the-heap.md
new file mode 100644
index 000000000..e2d4d3ac9
--- /dev/null
+++ b/src/doc/book/redirects/the-stack-and-the-heap.md
@@ -0,0 +1,13 @@
+% The Stack and the Heap
+
+<small>There is a new edition of the book and this is an old link.</small>
+
+> Both the stack and the heap are parts of memory that is available to your code to use at runtime, but they are structured in different ways.
+> The stack stores values in the order it gets them and removes the values in the opposite order.
+> All data on the stack must take up a known, fixed size.
+> For data with a size unknown to us at compile time or a size that might change, we can store data on the heap instead.
+
+---
+
+You can find the latest version of this information
+[here](ch04-01-what-is-ownership.html#the-stack-and-the-heap). \ No newline at end of file