E0277 could provide useful details

I was looking at trim_matches std docs code example and tried to inline x into the trim_matches` :
https://doc.rust-lang.org/std/primitive.str.html#method.trim_matches

#![allow(unused)]
fn main() {
assert_eq!("11foo1bar11".trim_matches('1'), "foo1bar");
assert_eq!("123foo1bar123".trim_matches(char::is_numeric), "foo1bar");

let x: &[_] = &['1', '2'];
// x inlined here:
assert_eq!("12foo1bar12".trim_matches( &['1', '2']), "foo1bar");
}

https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=c39b60b2edc4e1363c60c9c153372785

error[[E0277]](https://doc.rust-lang.org/nightly/error_codes/E0277.html): the trait bound `CharArrayRefSearcher<'_, '_, 2>: DoubleEndedSearcher<'_>` is not satisfied
 --> src/main.rs:8:40
  |
8 | assert_eq!("12foo1bar12".trim_matches( &['1', '2']), "foo1bar");
  |                          ------------  ^^^^^^^^^^^ the trait `DoubleEndedSearcher<'_>` is not implemented for `CharArrayRefSearcher<'_, '_, 2>`
  |                          |
  |                          required by a bound introduced by this call
  |
  = help: the following other types implement trait `DoubleEndedSearcher<'a>`:
            CharSearcher<'a>
            CharSliceSearcher<'a, 'b>
            CharPredicateSearcher<'a, F>
note: required by a bound in `core::str::<impl str>::trim_matches`
 --> /rustc/e5cfc55477eceed1317a02189fdf77a4a98f2124/library/core/src/str/mod.rs:2021:5

For more information about this error, try `rustc --explain E0277`.
error: could not compile `playground` (bin "playground") due to previous error

The diagnostic issued is not helping, mentioning 5 different structs 😅
I assume this is some kind of lifetime problem, but my first intuition was "should not matter if the reference to an array is coming from within our without the function call, since its a reference anyway?"
Would be great if the error could give some useful details.
I think we already have "lifetime only goes until here but should go until there for code to be valid` diagnostics somewhere, maybe we could use that and suggest using a var binding for the array?

Reproduce the trim_matches example and inspect the diagnostic around library/core/src/str/mod.rs:2021:5. Compare the E0277 output with existing lifetime diagnostics, then determine whether the array binding or lifetime context can be explained more usefully. Done means the reported error gives actionable details instead of primarily listing internal searcher types.