Merge pull request #3824 from elasota/specify-zero-offset
Specify offset 0 as invalid and specify required fixup behavior
This commit is contained in:
@@ -929,7 +929,10 @@ There is an exception though, when current sequence's `literals_length = 0`.
|
||||
In this case, repeated offsets are shifted by one,
|
||||
so an `offset_value` of 1 means `Repeated_Offset2`,
|
||||
an `offset_value` of 2 means `Repeated_Offset3`,
|
||||
and an `offset_value` of 3 means `Repeated_Offset1 - 1_byte`.
|
||||
and an `offset_value` of 3 means `Repeated_Offset1 - 1`.
|
||||
|
||||
In the final case, if `Repeated_Offset1 - 1` evaluates to 0, then the
|
||||
data is considered corrupted.
|
||||
|
||||
For the first block, the starting offset history is populated with following values :
|
||||
`Repeated_Offset1`=1, `Repeated_Offset2`=4, `Repeated_Offset3`=8,
|
||||
|
||||
Reference in New Issue
Block a user