Confusing error message for impl Trait consts/statics that use generics

[alexreg]

#53542 introduced impl Trait bindings in consts and statics (along with let bindings), but of course they cannot be assigned a value of a generic type. The error message is presently a bit confusing:

error[E0434]: can't capture dynamic environment in a fn item
  --> .../bindings.rs:4:29
   |
 4 |     const foo: impl Clone = x;
   |                             ^
   |
   = help: use the `|| { ... }` closure form instead

Example:

#![feature(impl_trait_in_bindings)]

fn a<T: Clone>(x: T) {
    const foo: impl Clone = x;
}

A message like cannot assign value of generic type to const or static of opaque type would be better, I think (unless there's already a suitable error that can be reused).

See also the bindings test from the above PR and its stderr.

CC @cramertj @oli-obk

[alexreg]

In fact, when trying to use a generic-typed const in a fn, the error messages aren't very good either!

Playground

Errors:

error[E0401]: can't use type parameters from outer function
 --> src/lib.rs:3:16
  |
2 | fn a<T: Clone>(x: T) {
  |    - - type variable from outer function
  |    |
  |    try adding a local type parameter in this method instead
3 |     const foo: T = x;
  |                ^ use of type variable from outer function

error[E0434]: can't capture dynamic environment in a fn item
 --> src/lib.rs:3:20
  |
3 |     const foo: T = x;
  |                    ^
  |
  = help: use the `|| { ... }` closure form instead

error: aborting due to 2 previous errors

[oli-obk]

duplicate of #51375 ?

[alexreg]

@oli-obk At the very least, I think it's closely related.

[estebank]

Current output:

error[E0435]: attempt to use a non-constant value in a constant
 --> src/lib.rs:5:29
  |
5 |     const foo: impl Clone = x;
  |                             ^ non-constant value

[traviscross]

We can close this as the feature was pulled out in #86729 and what was added back in #134185 only supports local bindings.