summaryrefslogtreecommitdiff
path: root/exercises/vecs/README.md
diff options
context:
space:
mode:
authormokou <mokou@fastmail.com>2022-07-12 15:16:25 +0200
committermokou <mokou@fastmail.com>2022-07-12 15:16:25 +0200
commit2f7fd513041c7c6275552650881a79b9120aaacf (patch)
tree0ce4f6afca30d729b1c23081004dc10aed28d32f /exercises/vecs/README.md
parent8e1f617d3402cb05b05c6737f60fbbfe74da4d78 (diff)
feat: move vec exercises into their own folder
Diffstat (limited to 'exercises/vecs/README.md')
-rw-r--r--exercises/vecs/README.md15
1 files changed, 15 insertions, 0 deletions
diff --git a/exercises/vecs/README.md b/exercises/vecs/README.md
new file mode 100644
index 0000000..ebe90bf
--- /dev/null
+++ b/exercises/vecs/README.md
@@ -0,0 +1,15 @@
+# Vectors
+
+Vectors are one of the most-used Rust data structures. In other programming
+languages, they'd simply be called Arrays, but since Rust operates on a
+bit of a lower level, an array in Rust is stored on the stack (meaning it
+can't grow or shrink, and the size needs to be known at compile time),
+and a Vector is stored in the heap (where these restrictions do not apply).
+
+Vectors are a bit of a later chapter in the book, but we think that they're
+useful enough to talk about them a bit earlier. We shall be talking about
+the other useful data structure, hash maps, later.
+
+## Further information
+
+- [Storing Lists of Values with Vectors](https://doc.rust-lang.org/stable/book/ch08-01-vectors.html)