Add support for types that can be records or tuples #153
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 support for "record tuples"; types that may be treated as either a record or a tuple by a
Stream
depending on its preference. The default preference is to treat these as records.The motivation for this is to support types that can be streamed as tuples in binary formats like protobuf, or as records in human-readable formats like JSON, such as:
Alternatively, this same type could be defined as a tuple:
If a record has any fields with
index
specified then all fields must have it. Likewise for tuples andlabel
.