rust/tests/ui/unwrap_or.stderr

error: use of `unwrap_or` followed by a function call
  --> $DIR/unwrap_or.rs:5:47
   |
LL |     let s = Some(String::from("test string")).unwrap_or("Fail".to_string()).len();
   |                                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `unwrap_or_else(|| "Fail".to_string())`
   |
   = note: `-D clippy::or-fun-call` implied by `-D warnings`

error: use of `unwrap_or` followed by a function call
  --> $DIR/unwrap_or.rs:11:47
   |
LL |     let s = Some(String::from("test string")).unwrap_or("Fail".to_string()).len();
   |                                               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `unwrap_or_else(|| "Fail".to_string())`

error: aborting due to 2 previous errors
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 08:56:12 -06:00			error: use of `unwrap_or` followed by a function call
Fix all the other tests 2023-05-31 12:47:10 -05:00			`--> $DIR/unwrap_or.rs:5:47`
Add license header to Rust files 2018-10-06 11:18:06 -05:00			`\|`
Update *.stderr files 2018-12-27 09:57:55 -06:00			`LL \| let s = Some(String::from("test string")).unwrap_or("Fail".to_string()).len();`
"try this" -> "try" 2023-07-01 06:08:01 -05:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `unwrap_or_else(\|\| "Fail".to_string())`
Add license header to Rust files 2018-10-06 11:18:06 -05:00			`\|`
			= note: `-D clippy::or-fun-call` implied by `-D warnings`
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 08:56:12 -06:00
Add newlines in unwrap_or ui test 2018-02-20 11:37:30 -06:00			error: use of `unwrap_or` followed by a function call
Automatic generation of error annotations for ui tests 2023-07-28 14:35:48 -05:00			`--> $DIR/unwrap_or.rs:11:47`
Adapt the *.stderr files of the ui-tests to the tool_lints 2018-08-01 09:30:44 -05:00			`\|`
Update *.stderr files 2018-12-27 09:57:55 -06:00			`LL \| let s = Some(String::from("test string")).unwrap_or("Fail".to_string()).len();`
"try this" -> "try" 2023-07-01 06:08:01 -05:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ help: try: `unwrap_or_else(\|\| "Fail".to_string())`
Add newlines in unwrap_or ui test 2018-02-20 11:37:30 -06:00
			`error: aborting due to 2 previous errors`
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 08:56:12 -06:00