Generated code causes warning: "type parameter goes unused in function definition"

[joshlf]

Fuchsia reports that, when updating to a more recent version of the Rust toolchain, code generated by zerocopy-derive causes the compiler to emit warnings:

warning: type parameter goes unused in function definition
  --> ../../src/sys/pkg/lib/far/rust/src/lib.rs:80:54
   |
80 | #[derive(PartialEq, Eq, Debug, Clone, Copy, Default, zerocopy::AsBytes, zerocopy::FromBytes)]
   |                                                      ^^^^^^^^^^^^^^^^^
   |
   = help: consider removing the parameter
   = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_type_parameters
   = note: `-D clippy::extra-unused-type-parameters` implied by `-D warnings`
   = note: this warning originates in the derive macro `zerocopy::AsBytes` (in Nightly builds, run with -Z macro-backtrace for more info)


warning: type parameter goes unused in function definition
  --> ../../src/sys/pkg/lib/far/rust/src/lib.rs:80:73
   |
80 | #[derive(PartialEq, Eq, Debug, Clone, Copy, Default, zerocopy::AsBytes, zerocopy::FromBytes)]
   |                                                                         ^^^^^^^^^^^^^^^^^^^
   |
   = help: consider removing the parameter
   = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#extra_unused_type_parameters
   = note: this warning originates in the derive macro `zerocopy::FromBytes` (in Nightly builds, run with -Z macro-backtrace for more info)

[djkoloski]

Looks like rust-lang/rust-clippy#10318

[joshlf]

Yep, agreed. I'm going to close this. If it turns out that's wrong and there's a different cause, we can re-open.