XCDRv1: support extra bytes in optional types (backport #285) #286
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.
Description
Some XCDRv1 implementations add extra bytes, usually alignment bytes, at the end of the serialized base type of an optional type. And this extra bytes are took into account in the parameter's length which describes the optional. Currently fastcdr doesn't support this. The parameter's length of a optional has to have the exact length of the serialized base type.
This PR introduces this flexibility to support other XCDRv1 implementations.
@Mergifyio backport 2.2.x
Contributor Checklist
versions.mdfile (if applicable).Reviewer Checklist
This is an automatic backport of pull request #285 done by [Mergify](https://mergify.com).