rust/tests/ui/issues/issue-50264-inner-deref-trait/option-as_deref.stderr

error[E0599]: the method `as_deref` exists for enum `Option<{integer}>`, but its trait bounds were not satisfied
  --> $DIR/option-as_deref.rs:2:29
   |
LL |     let _result = &Some(42).as_deref();
   |                             ^^^^^^^^
   |
   = note: the following trait bounds were not satisfied:
           `{integer}: Deref`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0599`.
Avoid describing a method as 'not found' when bounds are unsatisfied Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note. 2020-09-26 16:20:14 -05:00			error[E0599]: the method `as_deref` exists for enum `Option<{integer}>`, but its trait bounds were not satisfied
Stabilize Option::deref and Option::deref_mut The tracking issue https://github.com/rust-lang/rust/issues/50264 still has unresolved question for the corresponding `Result` methods. 2019-09-23 08:51:25 -05:00			`--> $DIR/option-as_deref.rs:2:29`
renamed `inner_deref` feature's `deref()` methods `as_deref()` as per discussion https://github.com/rust-lang/rust/issues/50264 2019-04-01 14:08:19 -05:00			`\|`
			`LL \| let _result = &Some(42).as_deref();`
Avoid describing a method as 'not found' when bounds are unsatisfied Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note. 2020-09-26 16:20:14 -05:00			`\| ^^^^^^^^`
renamed `inner_deref` feature's `deref()` methods `as_deref()` as per discussion https://github.com/rust-lang/rust/issues/50264 2019-04-01 14:08:19 -05:00			`\|`
Avoid describing a method as 'not found' when bounds are unsatisfied Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note. 2020-09-26 16:20:14 -05:00			`= note: the following trait bounds were not satisfied:`
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			`{integer}: Deref`
renamed `inner_deref` feature's `deref()` methods `as_deref()` as per discussion https://github.com/rust-lang/rust/issues/50264 2019-04-01 14:08:19 -05:00
			`error: aborting due to previous error`

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