runtime/expr: fix malformed empty record from record spread #4359
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.
A record spread expression that produces an empty record (e.g., "{...a}" evaluated with "this" bound to a Zed primitive value) results in a zed.Value with malformed bytes, which can cause a panic elsewhere. Fix this in recordSpreadExpr.Eval by returning a well-formed zed.Value.
For better or worse, we don't have any existing tests for malformed zed.Values, so I'm not adding one here.
Closes #4349.