rust/tests/ui/issues/issue-13497.stderr

error[E0106]: missing lifetime specifier
  --> $DIR/issue-13497.rs:2:5
   |
LL |     &str
   |     ^ expected named lifetime parameter
   |
   = help: this function's return type contains a borrowed value, but there is no value for it to be borrowed from
help: consider using the `'static` lifetime, but this is uncommon unless you're returning a borrowed value from a `const` or a `static`
   |
LL |     &'static str
   |      +++++++
help: instead, you are more likely to want to return an owned value
   |
LL |     String
   |     ~~~~~~

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0106`.
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`error[E0106]: missing lifetime specifier`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/issue-13497.rs:2:5`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| &str`
Tweak `'static` suggestion code Fix #71196. 2020-04-17 04:33:42 +00:00			`\| ^ expected named lifetime parameter`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00			`\|`
			`= help: this function's return type contains a borrowed value, but there is no value for it to be borrowed from`
On borrow return type, suggest borrowing from arg or owned return type When we encounter a function with a return type that has an anonymous lifetime with no argument to borrow from, besides suggesting the `'static` lifetime we now also suggest changing the arguments to be borrows or changing the return type to be an owned type. ``` error[E0106]: missing lifetime specifier --> $DIR/variadic-ffi-6.rs:7:6 \| LL \| ) -> &usize { \| ^ expected named lifetime parameter \| = help: this function's return type contains a borrowed value, but there is no value for it to be borrowed from help: consider using the `'static` lifetime, but this is uncommon unless you're returning a borrowed value from a `const` or a `static` \| LL \| ) -> &'static usize { \| +++++++ help: instead, you are more likely to want to change one of the arguments to be borrowed... \| LL \| x: &usize, \| + help: ...or alternatively, to want to return an owned value \| LL - ) -> &usize { LL + ) -> usize { \| ``` Fix #85843. 2023-11-14 20:36:49 +00:00			help: consider using the `'static` lifetime, but this is uncommon unless you're returning a borrowed value from a `const` or a `static`
Tweak `'static` suggestion code Fix #71196. 2020-04-17 04:33:42 +00:00			`\|`
			`LL \| &'static str`
Report elision failures on the AST. 2022-06-05 16:33:09 +00:00			`\| +++++++`
On borrow return type, suggest borrowing from arg or owned return type When we encounter a function with a return type that has an anonymous lifetime with no argument to borrow from, besides suggesting the `'static` lifetime we now also suggest changing the arguments to be borrows or changing the return type to be an owned type. ``` error[E0106]: missing lifetime specifier --> $DIR/variadic-ffi-6.rs:7:6 \| LL \| ) -> &usize { \| ^ expected named lifetime parameter \| = help: this function's return type contains a borrowed value, but there is no value for it to be borrowed from help: consider using the `'static` lifetime, but this is uncommon unless you're returning a borrowed value from a `const` or a `static` \| LL \| ) -> &'static usize { \| +++++++ help: instead, you are more likely to want to change one of the arguments to be borrowed... \| LL \| x: &usize, \| + help: ...or alternatively, to want to return an owned value \| LL - ) -> &usize { LL + ) -> usize { \| ``` Fix #85843. 2023-11-14 20:36:49 +00:00			`help: instead, you are more likely to want to return an owned value`
			`\|`
			`LL \| String`
			`\| ~~~~~~`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Move some `compile-fail` tests to `ui` 2018-07-15 21:11:54 +00:00
			For more information about this error, try `rustc --explain E0106`.