The problem is that raw_removeKeyRangeInternal already uses 1 and 2 in its implementation, right? So assert that the keys it is passed are not 1 and 2.
If for some reason that isn't how it is being used, at least add a comment next to the change so we don't ever use 1 and 2 again there.
The problem is that raw_removeKeyRa ngeInternal already uses 1 and 2 in its implementation, right? So assert that the keys it is passed are not 1 and 2.
If for some reason that isn't how it is being used, at least add a comment next to the change so we don't ever use 1 and 2 again there.