os-rust/src/test/ui/suggestions/issue-72766.stderr

error[E0277]: the `?` operator can only be applied to values that implement `Try`
  --> $DIR/issue-72766.rs:14:5
   |
LL |     SadGirl {}.call()?;
   |     ^^^^^^^^^^^^^^^^^^ the `?` operator cannot be applied to type `impl Future`
   |
   = help: the trait `Try` is not implemented for `impl Future`
note: required by `branch`
  --> $SRC_DIR/core/src/ops/try_trait.rs:LL:COL
   |
LL |     fn branch(self) -> ControlFlow<Self::Residual, Self::Output>;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
help: consider `await`ing on the `Future`
   |
LL |     SadGirl {}.call().await?;
   |                      ^^^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
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			error[E0277]: the `?` operator can only be applied to values that implement `Try`
Return early to avoid ICE 2020-05-30 18:48:54 +09:00			`--> $DIR/issue-72766.rs:14:5`
			`\|`
			`LL \| SadGirl {}.call()?;`
Tweak "use `.await`" suggestion 2020-10-21 14:25:09 -07:00			\| ^^^^^^^^^^^^^^^^^^ the `?` operator cannot be applied to type `impl Future`
Return early to avoid ICE 2020-05-30 18:48:54 +09: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 `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 11:13:50 -07: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 14:25:09 -07:00			help: consider `await`ing on the `Future`
			`\|`
			`LL \| SadGirl {}.call().await?;`
			`\| ^^^^^^`
Return early to avoid ICE 2020-05-30 18:48:54 +09:00
			`error: aborting due to previous error`

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