fix: exercise order - string before struct
The struct exercises rely on knowledge learned in the string exercises, so should follow rather than precede them.
This commit is contained in:
parent
9f61db5dbe
commit
2af0bf8d38
46
info.toml
46
info.toml
|
@ -218,6 +218,29 @@ Data Types -> The Tuple Type section of the book:
|
||||||
https://doc.rust-lang.org/book/ch03-02-data-types.html#the-tuple-type
|
https://doc.rust-lang.org/book/ch03-02-data-types.html#the-tuple-type
|
||||||
Now you have another tool in your toolbox!"""
|
Now you have another tool in your toolbox!"""
|
||||||
|
|
||||||
|
# STRINGS
|
||||||
|
|
||||||
|
[[exercises]]
|
||||||
|
name = "strings1"
|
||||||
|
path = "exercises/strings/strings1.rs"
|
||||||
|
mode = "compile"
|
||||||
|
hint = """
|
||||||
|
The `current_favorite_color` function is currently returning a string slice with the `'static`
|
||||||
|
lifetime. We know this because the data of the string lives in our code itself -- it doesn't
|
||||||
|
come from a file or user input or another program -- so it will live as long as our program
|
||||||
|
lives. But it is still a string slice. There's one way to create a `String` by converting a
|
||||||
|
string slice covered in the Strings chapter of the book, and another way that uses the `From`
|
||||||
|
trait."""
|
||||||
|
|
||||||
|
[[exercises]]
|
||||||
|
name = "strings2"
|
||||||
|
path = "exercises/strings/strings2.rs"
|
||||||
|
mode = "compile"
|
||||||
|
hint = """
|
||||||
|
Yes, it would be really easy to fix this by just changing the value bound to `word` to be a
|
||||||
|
string slice instead of a `String`, wouldn't it?? There is a way to add one character to line
|
||||||
|
9, though, that will coerce the `String` into a string slice."""
|
||||||
|
|
||||||
# STRUCTS
|
# STRUCTS
|
||||||
|
|
||||||
[[exercises]]
|
[[exercises]]
|
||||||
|
@ -254,29 +277,6 @@ For calculate_transport_fees: Bigger is more expensive usually, we don't have si
|
||||||
|
|
||||||
Have a look in The Book, to find out more about method implementations: https://doc.rust-lang.org/book/ch05-03-method-syntax.html"""
|
Have a look in The Book, to find out more about method implementations: https://doc.rust-lang.org/book/ch05-03-method-syntax.html"""
|
||||||
|
|
||||||
# STRINGS
|
|
||||||
|
|
||||||
[[exercises]]
|
|
||||||
name = "strings1"
|
|
||||||
path = "exercises/strings/strings1.rs"
|
|
||||||
mode = "compile"
|
|
||||||
hint = """
|
|
||||||
The `current_favorite_color` function is currently returning a string slice with the `'static`
|
|
||||||
lifetime. We know this because the data of the string lives in our code itself -- it doesn't
|
|
||||||
come from a file or user input or another program -- so it will live as long as our program
|
|
||||||
lives. But it is still a string slice. There's one way to create a `String` by converting a
|
|
||||||
string slice covered in the Strings chapter of the book, and another way that uses the `From`
|
|
||||||
trait."""
|
|
||||||
|
|
||||||
[[exercises]]
|
|
||||||
name = "strings2"
|
|
||||||
path = "exercises/strings/strings2.rs"
|
|
||||||
mode = "compile"
|
|
||||||
hint = """
|
|
||||||
Yes, it would be really easy to fix this by just changing the value bound to `word` to be a
|
|
||||||
string slice instead of a `String`, wouldn't it?? There is a way to add one character to line
|
|
||||||
9, though, that will coerce the `String` into a string slice."""
|
|
||||||
|
|
||||||
# TEST 2
|
# TEST 2
|
||||||
|
|
||||||
[[exercises]]
|
[[exercises]]
|
||||||
|
|
Loading…
Reference in a new issue