rust/src/test/ui/async-await/async-error-span.stderr

error[E0277]: `()` is not a future
  --> $DIR/async-error-span.rs:7:20
   |
LL | fn get_future() -> impl Future<Output = ()> {
   |                    ^^^^^^^^^^^^^^^^^^^^^^^^ `()` is not a future
   |
   = help: the trait `Future` is not implemented for `()`

error[E0698]: type inside `async fn` body must be known in this context
  --> $DIR/async-error-span.rs:13:9
   |
LL |     let a;
   |         ^ cannot infer type
   |
note: the type is part of the `async fn` body because of this `await`
  --> $DIR/async-error-span.rs:14:5
   |
LL |     get_future().await;
   |     ^^^^^^^^^^^^^^^^^^

error: aborting due to 2 previous errors

Some errors have detailed explanations: E0277, E0698.
For more information about an error, try `rustc --explain E0277`.
Adds a clearer message for when the async keyword is missing from a function Signed-off-by: Nell Shamrell <nellshamrell@gmail.com> 2020-06-18 10:30:47 -07:00			error[E0277]: `()` is not a future
Update tests 2020-02-06 10:33:05 +01:00			`--> $DIR/async-error-span.rs:7:20`
			`\|`
			`LL \| fn get_future() -> impl Future<Output = ()> {`
Adds a clearer message for when the async keyword is missing from a function Signed-off-by: Nell Shamrell <nellshamrell@gmail.com> 2020-06-18 10:30:47 -07:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^ `()` is not a future
Update tests 2020-02-06 10:33:05 +01: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 10:40:56 +03:00			= help: the trait `Future` is not implemented for `()`
Update tests 2020-02-06 10:33:05 +01:00
s/`async` fn/`async fn`/ 2019-10-02 14:39:44 -04:00			error[E0698]: type inside `async fn` body must be known in this context
Update tests 2020-02-06 10:33:05 +01:00			`--> $DIR/async-error-span.rs:13:9`
Improve error span for async type inference error Fixes #62382 Previously, we would point at the spawn of the 'await' expression, instead of the actual expression with an unknown type. 2019-07-04 14:20:04 -04:00			`\|`
			`LL \| let a;`
			`\| ^ cannot infer type`
			`\|`
s/`async` fn/`async fn`/ 2019-10-02 14:39:44 -04:00			note: the type is part of the `async fn` body because of this `await`
Update tests 2020-02-06 10:33:05 +01:00			`--> $DIR/async-error-span.rs:14:5`
Improve error span for async type inference error Fixes #62382 Previously, we would point at the spawn of the 'await' expression, instead of the actual expression with an unknown type. 2019-07-04 14:20:04 -04:00			`\|`
			`LL \| get_future().await;`
			`\| ^^^^^^^^^^^^^^^^^^`

Update tests 2020-02-06 10:33:05 +01:00			`error: aborting due to 2 previous errors`
Improve error span for async type inference error Fixes #62382 Previously, we would point at the spawn of the 'await' expression, instead of the actual expression with an unknown type. 2019-07-04 14:20:04 -04:00
Update tests 2020-02-06 10:33:05 +01:00			`Some errors have detailed explanations: E0277, E0698.`
			For more information about an error, try `rustc --explain E0277`.