mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
b6f580acc0
rust/src/test/ui/async-await/issue-61076.stderr

90 lines
3.0 KiB
Plaintext
Raw Normal View History

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 02:40:56 -05:00
error[E0277]: the `?` operator can only be applied to values that implement `Try`
suggest await before method
2020-08-20 02:34:08 -05:00
--> $DIR/issue-61076.rs:42:5
bless ui tests
2020-05-10 09:34:20 -05:00
|
LL | foo()?;
Tweak "use `.await`" suggestion
2020-10-21 16:25:09 -05:00
| ^^^^^^ the `?` operator cannot be applied to type `impl Future`
bless ui tests
2020-05-10 09:34:20 -05:00
|
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 02:40:56 -05:00
= help: the trait `Try` is not implemented for `impl Future`
Various diagnostics clean ups/tweaks * Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition
2021-07-17 13:13:50 -05:00
note: required by `branch`
--> $SRC_DIR/core/src/ops/try_trait.rs:LL:COL
|
LL | fn branch(self) -> ControlFlow<Self::Residual, Self::Output>;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Tweak "use `.await`" suggestion
2020-10-21 16:25:09 -05:00
help: consider `await`ing on the `Future`
|
LL | foo().await?;
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-21 21:07:19 -05:00
| ++++++
bless ui tests
2020-05-10 09:34:20 -05:00
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 02:40:56 -05:00
error[E0277]: the `?` operator can only be applied to values that implement `Try`
Tweak opaque type mismatch error
2021-07-31 14:20:00 -05:00
--> $DIR/issue-61076.rs:67:5
implement type_implments_trait query
2020-05-14 10:07:46 -05:00
|
LL | t?;
Tweak "use `.await`" suggestion
2020-10-21 16:25:09 -05:00
| ^^ the `?` operator cannot be applied to type `T`
implement type_implments_trait query
2020-05-14 10:07:46 -05:00
|
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 02:40:56 -05:00
= help: the trait `Try` is not implemented for `T`
Various diagnostics clean ups/tweaks * Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition
2021-07-17 13:13:50 -05:00
note: required by `branch`
--> $SRC_DIR/core/src/ops/try_trait.rs:LL:COL
|
LL | fn branch(self) -> ControlFlow<Self::Residual, Self::Output>;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Tweak "use `.await`" suggestion
2020-10-21 16:25:09 -05:00
help: consider `await`ing on the `Future`
|
LL | t.await?;
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-21 21:07:19 -05:00
| ++++++
implement type_implments_trait query
2020-05-14 10:07:46 -05:00
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 02:40:56 -05:00
error[E0609]: no field `0` on type `impl Future`
Tweak opaque type mismatch error
2021-07-31 14:20:00 -05:00
--> $DIR/issue-61076.rs:78:26
append more test cases for issue 61076
2020-05-30 09:57:12 -05:00
|
suggest await on field access
2020-08-16 07:25:22 -05:00
LL | let _: i32 = tuple().0;
Suggest calling await on method call and field access When encountering a failing method or field resolution on a `Future`, look at the `Output` and try the same operation on it. If successful, suggest calling `.await` on the `Future`. This had already been introduced in #72784, but at some point they stopped working.
2020-10-23 12:54:34 -05:00
| ^ field not available in `impl Future`, but it is available in its `Output`
|
help: consider `await`ing on the `Future` and access the field of its `Output`
|
LL | let _: i32 = tuple().await.0;
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-21 21:07:19 -05:00
| ++++++
append more test cases for issue 61076
2020-05-30 09:57:12 -05:00
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 02:40:56 -05:00
error[E0609]: no field `a` on type `impl Future`
Tweak opaque type mismatch error
2021-07-31 14:20:00 -05:00
--> $DIR/issue-61076.rs:82:28
append more test cases for issue 61076
2020-05-30 09:57:12 -05:00
|
suggest await on field access
2020-08-16 07:25:22 -05:00
LL | let _: i32 = struct_().a;
Suggest calling await on method call and field access When encountering a failing method or field resolution on a `Future`, look at the `Output` and try the same operation on it. If successful, suggest calling `.await` on the `Future`. This had already been introduced in #72784, but at some point they stopped working.
2020-10-23 12:54:34 -05:00
| ^ field not available in `impl Future`, but it is available in its `Output`
|
help: consider `await`ing on the `Future` and access the field of its `Output`
|
LL | let _: i32 = struct_().await.a;
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-21 21:07:19 -05:00
| ++++++
append more test cases for issue 61076
2020-05-30 09:57:12 -05:00
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 02:40:56 -05:00
error[E0599]: no method named `method` found for opaque type `impl Future` in the current scope
Tweak opaque type mismatch error
2021-07-31 14:20:00 -05:00
--> $DIR/issue-61076.rs:86:15
suggest await before method
2020-08-20 02:34:08 -05:00
|
LL | struct_().method();
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 02:40:56 -05:00
| ^^^^^^ method not found in `impl Future`
Suggest calling await on method call and field access When encountering a failing method or field resolution on a `Future`, look at the `Output` and try the same operation on it. If successful, suggest calling `.await` on the `Future`. This had already been introduced in #72784, but at some point they stopped working.
2020-10-23 12:54:34 -05:00
|
help: consider `await`ing on the `Future` and calling the method on its `Output`
|
LL | struct_().await.method();
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-21 21:07:19 -05:00
| ++++++
suggest await before method
2020-08-20 02:34:08 -05:00
suggest await on unexpected types
2020-08-20 05:42:08 -05:00
error[E0308]: mismatched types
Tweak opaque type mismatch error
2021-07-31 14:20:00 -05:00
--> $DIR/issue-61076.rs:94:9
suggest await on unexpected types
2020-08-20 05:42:08 -05:00
|
LL | Tuple(_) => {}
| ^^^^^^^^ expected opaque type, found struct `Tuple`
|
Tweak opaque type mismatch error
2021-07-31 14:20:00 -05:00
note: while checking the return type of the `async fn`
--> $DIR/issue-61076.rs:58:21
|
LL | async fn tuple() -> Tuple {
| ^^^^^ checked the `Output` of this `async fn`, expected opaque type
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 02:40:56 -05:00
= note: expected opaque type `impl Future`
suggest await on unexpected types
2020-08-20 05:42:08 -05:00
found struct `Tuple`
Add more `.await` suggestions on E0308
2020-10-22 21:03:36 -05:00
help: consider `await`ing on the `Future`
|
LL | match tuple().await {
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-06-21 21:07:19 -05:00
| ++++++
suggest await on unexpected types
2020-08-20 05:42:08 -05:00
error: aborting due to 6 previous errors
bless ui tests
2020-05-10 09:34:20 -05:00
suggest await on unexpected types
2020-08-20 05:42:08 -05:00
Some errors have detailed explanations: E0277, E0308, E0599, E0609.
append more test cases for issue 61076
2020-05-30 09:57:12 -05:00
For more information about an error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink