It's a relevant question. ArrayVec implements Drop, which precludes Copy.

I have considered making a Copy-only ArrayVec, but most of the hard things this library does are for the non-Copy part to be correct. The Copy case is simple, so a regular array is often enough.

Would you accept a CopyArrayVec pull-request?

I'm not sure, it requires duplicating the whole thing. As said above, the most interesting things ArrayVec does is handle the non-Copy case correctly.

I guess this is not what you want, but maybe specialization (unstable feature) can be used to make ArrayVec Copy exactly when its elements are Copy.

a PoC of copy-specialization works. This is the ideal approach since it transparently removes the overhead of non-copy arrayvecs (overwrite in drop etc). The use of unstable features is rather non-ideal though.

This issue isn't very high priority for me, I'm happy waiting until specialization stabilises if that suits you best 👍

We don't even know if specialization will allow this, but we'll see.

It sounds like this is no longer just a question but a feature request?

I'm not sure that this needs a breaking change.

arrayvec as a crate needs it. It's part of clearing the air before adding new features, if you will.

Where the most significant breaking change is the change of minimum Rust version

What is the status of this feature?

Is this maybe easier to do now with the new array based implementation in 0.7?

I’d be interested in this feature, is #193 on the right way to be merged ? thanks :)