You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation for #[automatically_derived] currently states:
The automatically_derived attribute is automatically added to implementations created by the derive attribute for built-in traits. It has no direct effect, but it may be used by tools and diagnostic lints to detect these automatically generated implementations.
I think the suggestion that this is only for built-in traits is incomplete; it's in use by many crates, including serde, clap, bevy, yew...
Also the "may be used by tools and diagnostic lints" seems vague: is this attribute recommended for use in derive macro output, for the purpose of suppressing clippy lints? Would this strategy be not recommended? I have seen a few github issues on proc-macro crates, and it does not seem like this attribute is well understood by crate authors.
The text was updated successfully, but these errors were encountered:
The documentation for
#[automatically_derived]
currently states:I think the suggestion that this is only for built-in traits is incomplete; it's in use by many crates, including serde, clap, bevy, yew...
Also the "may be used by tools and diagnostic lints" seems vague: is this attribute recommended for use in derive macro output, for the purpose of suppressing clippy lints? Would this strategy be not recommended? I have seen a few github issues on proc-macro crates, and it does not seem like this attribute is well understood by crate authors.
The text was updated successfully, but these errors were encountered: