tls_codec: add transparent VLBytes version#2267
Closed
kkohbrok wants to merge 3 commits into
Closed
Conversation
Contributor
|
@kkohbrok did you want to pick this up again at some point? |
Contributor
Author
|
Thanks for the reminder! This has effectively been resolved by #2322. |
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
2 participants
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.
This PR adds a version of VLBytes called
VLBytesFlat(I'm open to suggestions for a better name).In contrast to
VLBytes,VLBytesFlatis serde transparent. It can be used as a drop-in replacement for VLBytes and will deserialize instances of VLBytes correctly. As such, it can be used as a backwards-compatible drop-in.I didn't make the change directly to
VLBytesto not break applications such as OpenMLS that useVLBytesas keys for lookups.