2018-02-22 06:09:53 +00:00
|
|
|
// errors1.rs
|
2023-05-29 17:39:08 +00:00
|
|
|
//
|
|
|
|
// 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`. Thankfully, Rust has a similar
|
2023-08-25 19:49:22 +00:00
|
|
|
// construct to `Option` that can be used to express error conditions. Let's use
|
2023-05-29 17:39:08 +00:00
|
|
|
// it!
|
|
|
|
//
|
|
|
|
// Execute `rustlings hint errors1` or use the `hint` watch subcommand for a
|
|
|
|
// hint.
|
2016-02-16 23:14:20 +00:00
|
|
|
|
2019-11-11 12:38:24 +00:00
|
|
|
|
2024-04-26 06:18:06 +00:00
|
|
|
pub fn generate_nametag_text(name: String) -> Result<String, String> {
|
2022-02-08 23:46:22 +00:00
|
|
|
if name.is_empty() {
|
2024-04-26 06:18:06 +00:00
|
|
|
Err(format!("`name` was empty; it must be nonempty."))
|
2022-02-08 23:46:22 +00:00
|
|
|
} else {
|
2024-04-26 06:18:06 +00:00
|
|
|
Ok(format!("Hi! My name is {}", name))
|
2016-02-16 23:14:20 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
#[cfg(test)]
|
|
|
|
mod tests {
|
|
|
|
use super::*;
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn generates_nametag_text_for_a_nonempty_name() {
|
|
|
|
assert_eq!(
|
|
|
|
generate_nametag_text("Beyoncé".into()),
|
2022-04-14 08:25:44 +00:00
|
|
|
Ok("Hi! My name is Beyoncé".into())
|
2016-02-16 23:14:20 +00:00
|
|
|
);
|
|
|
|
}
|
|
|
|
|
|
|
|
#[test]
|
|
|
|
fn explains_why_generating_nametag_text_fails() {
|
|
|
|
assert_eq!(
|
|
|
|
generate_nametag_text("".into()),
|
2022-02-04 14:00:24 +00:00
|
|
|
// Don't change this line
|
2016-02-16 23:14:20 +00:00
|
|
|
Err("`name` was empty; it must be nonempty.".into())
|
|
|
|
);
|
|
|
|
}
|
|
|
|
}
|