diff options
| author | mokou <mokou@fastmail.com> | 2022-04-14 10:32:43 +0200 |
|---|---|---|
| committer | mokou <mokou@fastmail.com> | 2022-04-14 10:32:43 +0200 |
| commit | 76a36dd38594c63b4bd64e655efeb272ccfaf2a4 (patch) | |
| tree | c7be73bdff694750457f306afa883641f4f435df /exercises/error_handling | |
| parent | c39eb3fe551ec0ecfaa79c85b388426d1faa618a (diff) | |
chore: update errors1 comments and hint
Diffstat (limited to 'exercises/error_handling')
| -rw-r--r-- | exercises/error_handling/errors1.rs | 8 |
1 files changed, 2 insertions, 6 deletions
diff --git a/exercises/error_handling/errors1.rs b/exercises/error_handling/errors1.rs index 243622c..c417fb2 100644 --- a/exercises/error_handling/errors1.rs +++ b/exercises/error_handling/errors1.rs @@ -1,9 +1,8 @@ // errors1.rs // This function refuses to generate text to be printed on a nametag if // you pass it an empty string. It'd be nicer if it explained what the problem -// was, instead of just sometimes returning `None`. The 2nd test currently -// does not compile or pass, but it illustrates the behavior we would like -// this function to have. +// was, instead of just sometimes returning `None`. Thankfully, Rust has a similar +// construct to `Option` that can be used to express error conditions. Let's use it! // Execute `rustlings hint errors1` for hints! // I AM NOT DONE @@ -21,9 +20,6 @@ pub fn generate_nametag_text(name: String) -> Option<String> { mod tests { use super::*; - // This test passes initially if you comment out the 2nd test. - // You'll need to update what this test expects when you change - // the function under test! #[test] fn generates_nametag_text_for_a_nonempty_name() { assert_eq!( |
