30/01/2020 14:06, Trahe, Fiona: > We were unaware the LIST_END change could constitute an ABI breakage, but can > see how it affects the array size when picked up. > We're exploring options. > > I agree with Anoob's point that if we don't allow the LIST_END to be > modified, then it means no feature can be implemented without ABI breakage. > Anyone object to removing those LIST_END elements - or have a better > suggestion? Would have to be in 20.11 I suppose.
Yes, having max value right after the last value is ridiculous, it prevents adding any value. In 20.11, we should remove all these *_END and *_MAX from API enums and replace them with a separate #define with reasonnable maximums.
