mathieu/os-rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
os-rust/src/test/ui/async-await/suggest-missing-await.stderr

44 lines
1.3 KiB
Text
Raw Normal View History

Add suggestion for missing `.await` keyword
2019-06-19 21:55:18 +01:00
error[E0308]: mismatched types
Add more `.await` suggestions on E0308
2020-10-22 19:03:36 -07:00
--> $DIR/suggest-missing-await.rs:12:14
Add suggestion for missing `.await` keyword
2019-06-19 21:55:18 +01:00
|
LL | take_u32(x)
Tweak "use `.await`" suggestion
2020-10-21 14:25:09 -07:00
| ^ expected `u32`, found opaque type
Add suggestion for missing `.await` keyword
2019-06-19 21:55:18 +01:00
|
Tweak opaque type mismatch error
2021-07-31 12:20:00 -07:00
note: while checking the return type of the `async fn`
--> $DIR/suggest-missing-await.rs:5:24
|
LL | async fn make_u32() -> u32 {
| ^^^ checked the `Output` of this `async fn`, found opaque type
Specific labels when referring to "expected" and "found" types
2019-11-13 14:16:56 -08:00
= note: expected type `u32`
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
found opaque type `impl Future`
Tweak "use `.await`" suggestion
2020-10-21 14:25:09 -07:00
help: consider `await`ing on the `Future`
|
LL | take_u32(x.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 19:07:19 -07:00
| ++++++
Add suggestion for missing `.await` keyword
2019-06-19 21:55:18 +01:00
Emit coercion suggestions in more places Fixes #66910 We have several different kinds of suggestions we can try to make when type coercion fails. However, we were previously only emitting these suggestions from `demand_coerce_diag`. This resulted in the compiler failing to emit applicable suggestions in several different cases, such as when the implicit return value of a function had the wrong type. This commit adds a new `emit_coerce_suggestions` method, which tries to emit a number of related suggestions. This method is called from both `demand_coerce_diag` and `CoerceMany::coerce_inner`, which covers a much wider range of cases than before. We now suggest using `.await` in more cases where it is applicable, among other improvements.
2019-12-03 20:32:50 -05:00
error[E0308]: mismatched types
Add more `.await` suggestions on E0308
2020-10-22 19:03:36 -07:00
--> $DIR/suggest-missing-await.rs:22:5
Emit coercion suggestions in more places Fixes #66910 We have several different kinds of suggestions we can try to make when type coercion fails. However, we were previously only emitting these suggestions from `demand_coerce_diag`. This resulted in the compiler failing to emit applicable suggestions in several different cases, such as when the implicit return value of a function had the wrong type. This commit adds a new `emit_coerce_suggestions` method, which tries to emit a number of related suggestions. This method is called from both `demand_coerce_diag` and `CoerceMany::coerce_inner`, which covers a much wider range of cases than before. We now suggest using `.await` in more cases where it is applicable, among other improvements.
2019-12-03 20:32:50 -05:00
|
LL | dummy()
| ^^^^^^^ expected `()`, found opaque type
|
Tweak opaque type mismatch error
2021-07-31 12:20:00 -07:00
note: while checking the return type of the `async fn`
--> $DIR/suggest-missing-await.rs:18:18
|
LL | async fn dummy() {}
| ^ checked the `Output` of this `async fn`, found opaque type
Emit coercion suggestions in more places Fixes #66910 We have several different kinds of suggestions we can try to make when type coercion fails. However, we were previously only emitting these suggestions from `demand_coerce_diag`. This resulted in the compiler failing to emit applicable suggestions in several different cases, such as when the implicit return value of a function had the wrong type. This commit adds a new `emit_coerce_suggestions` method, which tries to emit a number of related suggestions. This method is called from both `demand_coerce_diag` and `CoerceMany::coerce_inner`, which covers a much wider range of cases than before. We now suggest using `.await` in more cases where it is applicable, among other improvements.
2019-12-03 20:32:50 -05:00
= note: expected unit 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 10:40:56 +03:00
found opaque type `impl Future`
Tweak "use `.await`" suggestion
2020-10-21 14:25:09 -07:00
help: consider `await`ing on the `Future`
Emit coercion suggestions in more places Fixes #66910 We have several different kinds of suggestions we can try to make when type coercion fails. However, we were previously only emitting these suggestions from `demand_coerce_diag`. This resulted in the compiler failing to emit applicable suggestions in several different cases, such as when the implicit return value of a function had the wrong type. This commit adds a new `emit_coerce_suggestions` method, which tries to emit a number of related suggestions. This method is called from both `demand_coerce_diag` and `CoerceMany::coerce_inner`, which covers a much wider range of cases than before. We now suggest using `.await` in more cases where it is applicable, among other improvements.
2019-12-03 20:32:50 -05:00
|
LL | dummy().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 19:07:19 -07:00
| ++++++
reword `;` suggestions to have consistent wording
2021-02-04 13:59:23 -08:00
help: consider using a semicolon here
Add more `.await` suggestions on E0308
2020-10-22 19:03:36 -07:00
|
LL | dummy();
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 19:07:19 -07:00
| +
Emit coercion suggestions in more places Fixes #66910 We have several different kinds of suggestions we can try to make when type coercion fails. However, we were previously only emitting these suggestions from `demand_coerce_diag`. This resulted in the compiler failing to emit applicable suggestions in several different cases, such as when the implicit return value of a function had the wrong type. This commit adds a new `emit_coerce_suggestions` method, which tries to emit a number of related suggestions. This method is called from both `demand_coerce_diag` and `CoerceMany::coerce_inner`, which covers a much wider range of cases than before. We now suggest using `.await` in more cases where it is applicable, among other improvements.
2019-12-03 20:32:50 -05:00
error: aborting due to 2 previous errors
Add suggestion for missing `.await` keyword
2019-06-19 21:55:18 +01:00
For more information about this error, try `rustc --explain E0308`.
Reference in a new issue Copy permalink