Inconsistent lifetime elision for `thread_local!`

I tried this code:

thread_local! {
    static WORKS: &i32 = const { &1 };
}

thread_local! {
    static FAILS: &i32 = &1;
}

I expected the thread-locals to either both compile or both fail to compile. Instead, only WORKS compiles, and FAILS doesn't:

error[E0106]: missing lifetime specifier
 --> src/lib.rs:6:19
  |
6 |     static FAILS: &i32 = &1;
  |                   ^ expected named lifetime parameter
  |
  = help: this function's return type contains a borrowed value, but there is no value for it to be borrowed from
help: consider using the `'static` lifetime, but this is uncommon unless you're returning a borrowed value from a `const` or a `static`
  |
6 |     static FAILS: &'static i32 = &1;
  |                    +++++++
help: instead, you are more likely to want to return an owned value
  |
6 -     static FAILS: &i32 = &1;
6 +     static FAILS: i32 = &1;
  |

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

The difference is that the WORKS expands into a const item of type &i32, while FAILS expands into a function item that returns type &i32. The former is legal lifetime elision, but the latter is not.

Meta

Reproducible on the playground with version 1.99.0-nightly (2026-07-20 87e5904f5eb6398af6b2)

Start with the expansion of the thread_local! macro, comparing the generated const item and function item that handle &i32. Reproduce the mismatch and add coverage establishing consistent lifetime-elision behavior for both forms; done means the supplied example no longer has divergent results.