rust/src/test/ui/async-await/suggest-missing-await-closure.stderr

error[E0308]: mismatched types
  --> $DIR/suggest-missing-await-closure.rs:16:18
   |
LL | async fn make_u32() -> u32 {
   |                        --- the `Output` of this `async fn`'s found opaque type
...
LL |         take_u32(x)
   |                  ^
   |                  |
   |                  expected `u32`, found opaque type
   |                  help: consider using `.await` here: `x.await`
   |
   = note:     expected type `u32`
           found opaque type `impl Future`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
Adjust tests wrt. 'async_closure' feature gate. 2019-07-02 04:12:29 +02:00			`error[E0308]: mismatched types`
			`--> $DIR/suggest-missing-await-closure.rs:16:18`
			`\|`
Point at opaque and closure type definitions in type errors 2019-11-15 18:53:17 -08:00			`LL \| async fn make_u32() -> u32 {`
review comment: wording 2019-12-15 22:48:45 -08:00			\| --- the `Output` of this `async fn`'s found opaque type
Point at opaque and closure type definitions in type errors 2019-11-15 18:53:17 -08:00			`...`
Adjust tests wrt. 'async_closure' feature gate. 2019-07-02 04:12:29 +02:00			`LL \| take_u32(x)`
			`\| ^`
			`\| \|`
Surround types with backticks in type errors 2019-11-15 09:37:01 -08:00			\| expected `u32`, found opaque type
Adjust tests wrt. 'async_closure' feature gate. 2019-07-02 04:12:29 +02:00			\| help: consider using `.await` here: `x.await`
			`\|`
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`
Adjust tests wrt. 'async_closure' feature gate. 2019-07-02 04:12:29 +02:00
			`error: aborting due to previous error`

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