chore: use auto-derived copy/clone impls

[nyurik]

Unless there is something really magical, it doesn't seem to make sense to have manual impl for the most commonly used traits

@rustbot label +stable-nominated

[rustbot]

r? @tgross35

rustbot has assigned @tgross35.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

[rustbot]

Some changes occurred in the Android module

cc @maurer

Some changes occurred in solarish module

cc @jclulow, @pfmooney

Some changes occurred in OpenBSD module

cc @semarie

[tgross35]

I'm not sure if it would work but you can try adding ::core::prelude::v1::derive to the prelude at

libc/src/macros.rs

Line 65 in 0fe1d45

macro_rules! prelude {

, since that isn't in scope by default when building as part of std.

[nyurik]

@tgross35 thx, but I am still getting a really strange warning in the style check -- what is an s! macro, and why rust/clippy suggests it?

error: impl Copy and Clone manually
  --> /home/runner/work/libc/libc/libc-test/../src/fuchsia/mod.rs:84:3
   |
84 | #[derive(Clone, Copy)]
   |   ^^^^^^^^^^^^^^^^^^^ found manual implementation of Copy and/or Clone
   |
   = help: use one of the s! macros instead

[tgross35]

Most of the binding structs are wrapped in s! which adds the trait implementations. For enums, e! should do the same.

@rustbot author

[rustbot]

Reminder, once the PR becomes ready for a review, use @rustbot ready.