From e41696461e802e02f754ed531735b65802b24a24 Mon Sep 17 00:00:00 2001 From: Ilya Garazha Date: Thu, 19 Dec 2024 17:15:54 +0300 Subject: [PATCH] Update immutable.md tiny typo --- docs/src/immutable.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/immutable.md b/docs/src/immutable.md index 36bc86b..c971e71 100644 --- a/docs/src/immutable.md +++ b/docs/src/immutable.md @@ -103,7 +103,7 @@ And the last line, comparing `y` and `x` with `===` confirms that these two labe ## Heap and Stack memory -The distinction between mutable and mutable objects have important distinctions when it comes to performance. These distinctions are associated to the assumptions that the compiler can make about the behavior of these variables and, thus, about how they can be stored in the memory. +The distinction between mutable and immutable objects have important distinctions when it comes to performance. These distinctions are associated to the assumptions that the compiler can make about the behavior of these variables and, thus, about how they can be stored in the memory. In particular, there are two major ways in which values (numbers, objects, arrays), can be stored in memory: in the *heap* or in the *stack*. Very roughly, the *heap* is the most flexible form of storing objects, and probably the one that maps more clearly into our naive intuitions about how memory works. In the *heap* the objects have addresses, which point to the actual positions in the memory where the objects are located. For example, ```julia