false positive `dead_code` "never constructed" warning on 1.80.0 for a `struct` where the constructor takes `&'static self` about rust HOT 11 OPEN

In the real code the &'static self does get used of course, but as I was minimizing it I found that it wasn't necessary to see the warning. The 'static itself is not necessary to see the warning either, but in this case I think the only way to call init in safe rust is with a static, so I included it for clarity.

from rust.

How do you wind up with the &'static self in the original code, is it via FFI? If so, #126169 / #127104 may be relevant. (If this was 1.80 then it happend before that, similar code though).

from rust.

The example I pasted shows how the &'static self is obtained: static FOO: Foo = FOO.init(7);
This part matches exactly what the original code was doing. I'm not using any repr attribute in this example so I'm not sure it's related to those issues (I did notice those while searching for dups). The warning should fire for Foo if the init function didn't exist, but init constructs Foo.

from rust.

Completely missed the example, thanks. This is a pretty weird case considering self is the parameter that doesn't get used.

from rust.