Overflow evaluating requirement for an unusued type when function has generic lifetime parameters

[JackStade]

I tried this code:

#![recursion_limit = "8"]

use std::ops::Mul;

fn test<'a, T: 'a>() {
    17 * Foo;
}

#[derive(Clone, Copy)]
struct Foo;

impl Mul<Foo> for u32 {
    type Output = u32;
    
    fn mul(self, other: Foo) -> u32 {
        self
    }
}

struct Wrap<T>{
    t: T,
}

impl<T: Copy> Mul<Wrap<T>> for u32 where u32: Mul<T, Output = T> {
    type Output = Wrap<T>;
    
    fn mul(self, other: Wrap<T>) -> Self::Output {
        Wrap {
            t: self * other.t,
        }
    }
}

I would expect this compile.

Instead, I get this error:

error[[E0275]](https://doc.rust-lang.org/stable/error_codes/E0275.html): overflow evaluating the requirement `u32: Mul<Wrap<_>>`
  --> src/lib.rs:6:8
   |
6  |     17 * Foo;
   |        ^
   |
   = help: consider increasing the recursion limit by adding a `#![recursion_limit = "16"]` attribute to your crate (`playground`)
note: required for `u32` to implement `Mul<Wrap<Wrap<_>>>`
  --> src/lib.rs:25:15
   |
25 | impl<T: Copy> Mul<Wrap<T>> for u32 where u32: Mul<T, Output = T> {
   |               ^^^^^^^^^^^^     ^^^                   ---------- unsatisfied trait bound introduced here
   = note: 6 redundant requirements hidden
   = note: required for `u32` to implement `Mul<Wrap<Wrap<Wrap<Wrap<Wrap<Wrap<Wrap<Wrap<_>>>>>>>>>`

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

I reduced the recursion limit to make the output smaller, but this still happens with default recursion.

The function test doesn't involve the type Wrap at all. If everything involving Wrap is removed then the code compiles.

If the function test is removed or the (unused) generic parameters are removed, then the code compiles.

In order for the bug to occur, the function test needs to have a lifetime parameter and another parameter which depends on that lifetime parameter (the signature fn test<'a, 'b: 'a>() also causes the bug). I couldn't get this to happen without using lifetimes.

Several closely related issues have been mentioned in this thread: #39959. Some of the specific behavior here seems unique to this example as far as I can tell.

Meta

rustc --version --verbose:

rustc 1.70.0 (90c541806 2023-05-31)
binary: rustc
commit-hash: 90c541806f23a127002de5b4038be731ba1458ca
commit-date: 2023-05-31
host: x86_64-unknown-linux-gnu
release: 1.70.0
LLVM version: 16.0.2