Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed in #78, section 4.2 can be interpreted in different ways. But even if you interpret it in the most restrictive way (all table size updates MUST occur at the beginning of a header block), it's only a MUST for the encoder. It says nowhere that the decoder "MUST treat this as a decoding error", which is what the test is checking.
So I don't think there's anything wrong with a decoder that accepts table size updates in the middle of a header block, because it's still perfectly compatible with encoders that follow the other interpretation. For encoders, it's probably safer to be more strict in order to be compatible with all decoders.