summaryrefslogtreecommitdiff
path: root/info.toml
diff options
context:
space:
mode:
authorRoberto Vidal <vidal.roberto.j@gmail.com>2019-11-14 08:20:38 +0100
committerRoberto Vidal <vidal.roberto.j@gmail.com>2019-11-14 08:21:56 +0100
commitb565c4d3e74e8e110bef201a082fa1302722a7c3 (patch)
treeef776a3ddee5a27c6c80332b213ec777b99b3fb2 /info.toml
parente9a835c1c01dacdb017774f8fb5de22c86602db5 (diff)
fix: line numbers in several exercises and hints
The introduction of `I AM NOT DONE` shifted the lines of all exercises, which now need adjustment.
Diffstat (limited to 'info.toml')
-rw-r--r--info.toml14
1 files changed, 7 insertions, 7 deletions
diff --git a/info.toml b/info.toml
index 743ce2b..99628d1 100644
--- a/info.toml
+++ b/info.toml
@@ -5,7 +5,7 @@ name = "variables1"
path = "exercises/variables/variables1.rs"
mode = "compile"
hint = """
-Hint: The declaration on line 5 is missing a keyword that is needed in Rust
+Hint: The declaration on line 12 is missing a keyword that is needed in Rust
to create a new variable binding."""
[[exercises]]
@@ -15,7 +15,7 @@ mode = "compile"
hint = """
The compiler message is saying that Rust cannot infer the type that the
variable binding `x` has with what is given here.
-What happens if you annotate line 5 with a type annotation?
+What happens if you annotate line 7 with a type annotation?
What if you give x a value?
What if you do both?
What type should x be, anyway?
@@ -36,7 +36,7 @@ path = "exercises/variables/variables4.rs"
mode = "compile"
hint = """
Oops! In this exercise, we have a variable binding that we've created on
-line 5, and we're trying to use it on line 6, but we haven't given it a
+line 7, and we're trying to use it on line 8, but we haven't given it a
value. We can't print out something that isn't there; try giving x a value!
This is an error that can cause bugs that's very easy to make in any
programming language -- thankfully the Rust compiler has caught this for us!"""
@@ -365,8 +365,8 @@ name = "move_semantics1"
path = "exercises/move_semantics/move_semantics1.rs"
mode = "compile"
hint = """
-So you've got the "cannot borrow immutable local variable `vec1` as mutable" error on line 11,
-right? The fix for this is going to be adding one keyword, and the addition is NOT on line 11
+So you've got the "cannot borrow immutable local variable `vec1` as mutable" error on line 13,
+right? The fix for this is going to be adding one keyword, and the addition is NOT on line 13
where the error is."""
[[exercises]]
@@ -375,8 +375,8 @@ path = "exercises/move_semantics/move_semantics2.rs"
mode = "compile"
hint = """
So `vec0` is being *moved* into the function `fill_vec` when we call it on
-line 7, which means it gets dropped at the end of `fill_vec`, which means we
-can't use `vec0` again on line 10 (or anywhere else in `main` after the
+line 10, which means it gets dropped at the end of `fill_vec`, which means we
+can't use `vec0` again on line 13 (or anywhere else in `main` after the
`fill_vec` call for that matter). We could fix this in a few ways, try them
all!
1. Make another, separate version of the data that's in `vec0` and pass that