For now, only high-level review.
The main cost of sorting is interface complexity: we need to specify
which things are sorted, and what the sorting order is (see your TODO
below). Once we've done so, we can't go back.
There's also implementation complexity, but your patch shows it's low
enough
On 10/30/2015 05:20 AM, Markus Armbruster wrote:
> For now, only high-level review.
>
> The main cost of sorting is interface complexity: we need to specify
> which things are sorted, and what the sorting order is (see your TODO
> below). Once we've done so, we can't go back.
>
> There's also
Sorting the values of an enum makes it easier to look up whether
a particular value is present, via binary rather than linear search
(probably most visible with QKeyCode, which has grown over
several releases). Additionally, QMP clients need not know which
C value is associated with an enum name,
