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

error[E0599]: the method `as_deref_mut` exists for enum `Option<{integer}>`, but its trait bounds were not satisfied
  --> $DIR/option-as_deref_mut.rs:2:33
   |
LL |     let _result = &mut Some(42).as_deref_mut();
   |                                 ^^^^^^^^^^^^
   |
   = 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 17:20:14 -04:00			error[E0599]: the method `as_deref_mut` 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 15:51:25 +02:00			`--> $DIR/option-as_deref_mut.rs:2:33`
renamed `inner_deref` feature's `deref()` methods `as_deref()` as per discussion https://github.com/rust-lang/rust/issues/50264 2019-04-01 12:08:19 -07:00			`\|`
			`LL \| let _result = &mut Some(42).as_deref_mut();`
Improve method name suggestions Attempts to improve method name suggestions when a matching method name is not found. The approach taken is use the Levenshtein distance and account for substrings having a high distance but can sometimes be very close to the intended method (eg. empty vs is_empty). 2022-03-14 21:07:19 +00:00			`\| ^^^^^^^^^^^^`
renamed `inner_deref` feature's `deref()` methods `as_deref()` as per discussion https://github.com/rust-lang/rust/issues/50264 2019-04-01 12:08:19 -07: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 17:20:14 -04:00			`= note: the following trait bounds were not satisfied:`
tests 2021-10-08 01:38:33 +02: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 12:08:19 -07:00
			`error: aborting due to previous error`

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