`no-copy` flag unexpectedly removes `Clone` derive as well

Input C/C++ Header

struct Bytes {
    char bytes[1024];
};

Bindgen Invocation

$ bindgen input.h --no-copy Bytes

Actual Results

/* automatically generated by rust-bindgen 0.64.0 */

#[repr(C)]
#[derive(Debug)]
pub struct Bytes {
    pub bytes: [::std::os::raw::c_char; 1024usize],
}

Expected Results

By default bindgen adds Copy and Clone derives. Using --no-copy should only remove the Copy derivation. Types like these are too big to be Copy but are ok to be explicitly Cloned. TLDR:

/* automatically generated by rust-bindgen 0.64.0 */

#[repr(C)]
#[derive(Debug, Clone)]
pub struct Bytes {
    pub bytes: [::std::os::raw::c_char; 1024usize],
}

Reproduce the issue with the shown C++ header and bindgen input.h --no-copy Bytes invocation, then trace how derives are selected for the generated Bytes type. Done means --no-copy removes Copy while retaining Clone, producing the expected derives.