Fix regression of cost behavior for has() #651
Merged
Conversation
This file contains 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
jpbetz
reviewed
Mar 3, 2023
jpbetz
reviewed
Mar 3, 2023
jpbetz
reviewed
Mar 3, 2023
DangerOnTheRanger
force-pushed
the
evalTestOnly-fix
branch
from
0320b5a to
22aee46
Compare
jpbetz
changed the title
jpbetz
changed the title
jpbetz
reviewed
Mar 3, 2023
|
/gcbrun |
TristonianJones
previously approved these changes
Mar 3, 2023
|
/gcbrun |
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.
This PR adds a hack that records the presence of
fieldTypeonevalTestOnlyin order to report a different cost whenfieldTypeis present.