Use schema in TPE to reduce has/hasTag/in/==/is - #997
Open
john-h-kastner-aws wants to merge 1 commit into
Open
Conversation
Extends the TPE model so that `has`, `hasTag`, `in`, `==`, and `is` reduce to literals when type information in the schema (plus error-freedom) is enought to reach a concrete value. Signed-off-by: jkastner <jkastner@amazon.com>
john-h-kastner-aws
force-pushed
the
tpe-has-reduction-proof
branch
from
July 29, 2026 17:20
68f25fa to
6768f69
Compare
14 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Extends the TPE model so that
has,hasTag,in,==, andisreduce to literals when type information in the schema (plus error-freedom) is enough to reach a concrete value.Large diff because
TPE.evaluatenow needs a schema.Key changes addings this functions with calls at appropriate sites.
Issue #, if available:
Description of changes: