Moving `ArrayVec` has complexity O(capacity()) instead of O(len())

newpavlov February 13, 2018, 9:55am 3

I guess it’s an additional use-case for move constructors in one form or another. One of the previous discussions.

Topic		Replies	Views
The way to see how memcpy and alloca introduced by move is optimized compiler	3	1068	July 14, 2023
Add `push`, `push_back`, `pop` & `pop_back` methods to fixed-size arrays libs	39	2916	July 25, 2022
Idea: `shift_move` to efficiently move elements in a `Vec` libs	6	663	January 21, 2025
Vec! lack of optimization for "zeroed" types libs	11	1225	August 26, 2018
Defer memcpy when passing types that is !Copy until it is actually moved to another variable	4	1431	July 16, 2022