rust-clippy/tests/ui/unwrap_or.rs

#![warn(clippy::all, clippy::or_fun_call)]
#![allow(clippy::unnecessary_literal_unwrap)]

fn main() {
    let s = Some(String::from("test string")).unwrap_or("Fail".to_string()).len();
}

fn new_lines() {
    let s = Some(String::from("test string")).unwrap_or("Fail".to_string()).len();
}
Make it clear that `or_fun_call` can be a false-positive Also move it to nursery so that the false-positives can be dealt with. CC #8574 2022-11-12 21:26:09 +00:00			`#![warn(clippy::all, clippy::or_fun_call)]`
Fix all the other tests 2023-05-31 17:47:10 +00:00			`#![allow(clippy::unnecessary_literal_unwrap)]`
Fix: point to correct problem part of code Fix span so it no longer contains the whole train-wreck of code and only points to the problem function (for the unwrap_or lint). https://github.com/rust-lang-nursery/rust-clippy/issues/2422 Update ui test methods - it had several cases where the error message span is now shorter 2018-02-15 14:56:12 +00:00
			`fn main() {`
			`let s = Some(String::from("test string")).unwrap_or("Fail".to_string()).len();`
			`}`
Add newlines in unwrap_or ui test 2018-02-20 17:37:30 +00:00
			`fn new_lines() {`
rustfmt tests 2018-12-09 22:26:16 +00:00			`let s = Some(String::from("test string")).unwrap_or("Fail".to_string()).len();`
Add newlines in unwrap_or ui test 2018-02-20 17:37:30 +00:00			`}`