type in expression position followed by `::` should suggest `<...>::`

[durka]

When you write a macro that tries to call a method on the type...

macro_rules! call {
    ($t:ty) => {
        $t::foo()
    }
}

...and try to call it...

call!(Foo);

...you get an error that doesn't make any sense:

error: expected expression, found `Foo`
  --> expr.rs:18:45
   |
18 |     match {macro_rules! call { ($t:ty) => { $t::foo() } } call!(Foo);} {
   |                                             ^^            ----------- in this macro invocation
   |                                             |
   |                                             expected expression

The syntax that works is <$t>::foo(), but there's no way to discover this, so the error message should suggest it.

cc @eddyb

[petrochenkov]

Similar to #52307.

Parser already have necessary infra for making these suggestions, but it doesn't apply in this specific case for some reason.

error: missing angle brackets in associated item path
 --> src/main.rs:2:13
  |
2 |     let x = [u8; 1]::clone();
  |             ^^^^^^^^^^^^^^ help: try: `<[u8; 1]>::clone`

https://play.rust-lang.org/?gist=655aea8c484b9a47fef838d3dc74b395&version=nightly&mode=debug&edition=2015

[petrochenkov]

Fixed in #59058