Add support for custom Vals with materialization logic #571
Conversation
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
He-Pin
reviewed
Dec 16, 2025
Author
|
@He-Pin Moved the materialize logic into Materializable |
He-Pin
reviewed
Dec 17, 2025
stephenamar-db
approved these changes
Dec 17, 2025
Co-authored-by: He-Pin(kerr) <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
We would like to add better support for custom
Valtypes. These can already be created by extendingVal.Literal, but can't be materialized, sinceMaterializerdoesn't know what to do with them.This PR allows specifying the materialization logic to use with custom
Vals.