red/rustlings
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Address review comments. Fix typos, sentence formatting.

Browse source
This commit is contained in:
Sateesh Basavaraju 2021-05-08 16:15:10 +05:30
parent 9b3e700edf
commit f3663eeb93
2 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
exercises/option/option3.rs
View file

@ -1,4 +1,4 @@
// option2.rs
// option3.rs
// Make me compile! Execute `rustlings hint option3` for hints
// I AM NOT DONE

9
info.toml
View file

@ -214,7 +214,12 @@ So the end goal is to:
name = "move_semantics5"
path = "exercises/move_semantics/move_semantics5.rs"
mode = "compile"
hint = """Carefully reason about the range in which each mutable reference is in vogue. Does updating the value of referrent (x) immediately after the mutable reference is taken helps ? Read more about 'Mutable Referenes' in the book's section References and Borrowing': https://doc.rust-lang.org/book/ch04-02-references-and-borrowing.html#mutable-references."""
hint = """
Carefully reason about the range in which each mutable reference is in
vogue. Does updating the value of referrent (x) immediately after the
mutable reference is taken helps? Read more about 'Mutable Referenes'
in the book's section References and Borrowing':
https://doc.rust-lang.org/book/ch04-02-references-and-borrowing.html#mutable-references."""
# PRIMITIVE TYPES
@ -591,7 +596,7 @@ path = "exercises/option/option3.rs"
mode = "compile"
hint = """
The compiler says a partial move happened in the `match`
statement. How can this be avoided ? The compiler shows the correction
statement. How can this be avoided? The compiler shows the correction
needed. After making the correction as suggested by the compiler, do
read: https://doc.rust-lang.org/std/keyword.ref.html"""