fixes #121: java serialization breaks serializedSize #122
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.
Previously -1 was used as a sentinel value.
However, if a generated case class to be serialized using java serialization,
all backing fields would be reset to 0 because java serialization does not call
constructors.
This fix changes serializedSize default (sentinel) value to 0.
Serialized size of 0 is valid value and it will not be cached if the message
is actually empty.
Still, for such messages computing size should be cheap.