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

error[E0277]: `?` couldn't convert the error to `()`
  --> $DIR/issue-32709.rs:4:11
   |
LL | fn a() -> Result<i32, ()> {
   |           --------------- expected `()` because of this
LL |     Err(5)?;
   |           ^ the trait `From<{integer}>` is not implemented for `()`
   |
   = note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
   = help: the following other types implement trait `From<T>`:
             <(T,) as From<[T; 1]>>
             <(T, T) as From<[T; 2]>>
             <(T, T, T) as From<[T; 3]>>
             <(T, T, T, T) as From<[T; 4]>>
             <(T, T, T, T, T) as From<[T; 5]>>
             <(T, T, T, T, T, T) as From<[T; 6]>>
             <(T, T, T, T, T, T, T) as From<[T; 7]>>
             <(T, T, T, T, T, T, T, T) as From<[T; 8]>>
           and 4 others
   = note: required for `Result<i32, ()>` to implement `FromResidual<Result<Infallible, {integer}>>`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
Give custom error for E0277 on `?` error case 2019-04-17 19:50:50 -07:00			error[E0277]: `?` couldn't convert the error to `()`
Point at try `?` on errors affecting the err match arm of the desugared code 2019-04-17 18:30:26 -07:00			`--> $DIR/issue-32709.rs:4:11`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
Point at the return type on `.into()` failure caused by `?` Fix #35946. 2020-04-21 17:20:12 -07:00			`LL \| fn a() -> Result<i32, ()> {`
			\| --------------- expected `()` because of this
Update tests 2019-03-09 15:03:44 +03:00			`LL \| Err(5)?;`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 10:40:56 +03:00			\| ^ the trait `From<{integer}>` is not implemented for `()`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00			`\|`
Explain that ? converts the error type using From 2019-05-17 12:18:56 -07:00			= note: the question mark operation (`?`) implicitly performs a conversion on the error value using the `From` trait
--bless tests 2022-06-02 13:14:43 +04:00			= help: the following other types implement trait `From<T>`:
Don't sort strings right after we just sorted by types 2023-06-27 23:31:06 +00:00			`<(T,) as From<[T; 1]>>`
--bless tests 2022-06-02 13:14:43 +04:00			`<(T, T) as From<[T; 2]>>`
			`<(T, T, T) as From<[T; 3]>>`
			`<(T, T, T, T) as From<[T; 4]>>`
			`<(T, T, T, T, T) as From<[T; 5]>>`
			`<(T, T, T, T, T, T) as From<[T; 6]>>`
			`<(T, T, T, T, T, T, T) as From<[T; 7]>>`
			`<(T, T, T, T, T, T, T, T) as From<[T; 8]>>`
			`and 4 others`
Reword "Required because of the requirements on the impl of ..." 2022-08-15 21:31:37 +01:00			= note: required for `Result<i32, ()>` to implement `FromResidual<Result<Infallible, {integer}>>`
Move some `compile-fail` tests to `ui` 2018-07-15 14:11:54 -07:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0277`.