summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorliv <mokou@fastmail.com>2023-09-04 14:39:28 +0200
committerGitHub <noreply@github.com>2023-09-04 14:39:28 +0200
commit14fbdd20ac53e0226ad4ac28a1642946a89471bc (patch)
treec449b718ca8edf61be0755086ff08733907f8184
parenta5fe578e79914faf932cb8cd2d200a12d9e1af39 (diff)
parentad0fad4218d0baa9f6cb24d3292637d0f21aac52 (diff)
Merge pull request #1473 from Jak-Ch-ll/update-hints-for-vecs2
docs(vecs2): update hints
-rw-r--r--info.toml13
1 files changed, 6 insertions, 7 deletions
diff --git a/info.toml b/info.toml
index c0bead9..c84dfa5 100644
--- a/info.toml
+++ b/info.toml
@@ -268,15 +268,14 @@ name = "vecs2"
path = "exercises/vecs/vecs2.rs"
mode = "test"
hint = """
-Hint 1: In the code, the variable `element` represents an item from the Vec as it is being iterated.
-Can you try multiplying this?
+In the first function we are looping over the Vector and getting a reference to one `element` at a time.
+To modify the value of that `element` we need to use the * dereference operator. You can learn more in this chapter of the Rust book:
+https://doc.rust-lang.org/stable/book/ch08-01-vectors.html#iterating-over-the-values-in-a-vector
-Hint 2: For the first function, there's a way to directly access the numbers stored
-in the Vec, using the * dereference operator. You can both access and write to the
-number that way.
+In the second function this dereferencing is not necessary, because the map function expects the new value to be returned.
-After you've completed both functions, decide for yourself which approach you like
-better. What do you think is the more commonly used pattern under Rust developers?
+After you've completed both functions, decide for yourself which approach you like better.
+What do you think is the more commonly used pattern under Rust developers?
"""
# MOVE SEMANTICS