Latest nightly compiler reports dead_code warnings for structs with private fields #3740
Labels
C-bug
Category: bug
Comments
|
I don't think the change is going to get reverted or changed IMO. One workaround would be to add |
Dajamante
added a commit
to ferrocene/ferrocene
that referenced
this issue
Jun 13, 2024
added dead_code lint while this needs fix: rust-lang/libc#3740 deleted Makefiles annotations are still covered - ferrocene-annotations: um_rustc_C_link_args - ferrocene-annotations: um_rustc_C_codegen_units - ferrocene-annotations: um_rustc_C_prefer_dynamic
Dajamante
added a commit
to ferrocene/ferrocene
that referenced
this issue
Jun 14, 2024
added dead_code lint while this needs fix: rust-lang/libc#3740
|
With rust-lang/rust#128404, I think this has been resolved. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometime in the last week the rustc nightly compiler got more aggressive about reporting
dead_codewarnings. It now warns whenever a struct contains a private field but no constructor. That catches many structs in libc, which are intended to be initialized withstd::mem::zeroed(). IMHO this is a rustc bug. This ought to be a separate lint so it can be silenced without silencing all dead_code warnings.Here's an example build failure:
https://cirrus-ci.com/task/6392171014651904?logs=test#L17
The text was updated successfully, but these errors were encountered: