Repository navigation
Assert complete persisted H264 parameter records - #6
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Strengthen the regression coverage associated with vlang/v#29305. The existing storage tests compared copied sizeof(variable) bytes to the same sizeof(variable), so a pointer-sized copy could satisfy both sides. Use the explicit record type size and assert recovered nonzero SPS/PPS IDs. Also verify that custom scaling lists survive a complete stored-record copy.
No parser API or behavior changes. Local released V 0.5.2/TinyCC, clean upstream strict V3/TinyCC, and strict V3/GCC tests pass. Linux and Windows CI will verify the expanded tests.