Fix expr string cast #1999
Merged
Fix expr string cast #1999
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
rajyan
force-pushed
the
fix-expr-string-cast
branch
from
5982104 to
7fd3efb
Compare
|
This pull request has been marked as ready for review. |
|
Wait, found an edge case Maybe we should make type specifier don't specify scalar types. |
|
On second thought, this was fine, because it wouldn't converted to integer if used as array keys. |
|
This pull request has been marked as ready for review. |
|
Thank you! |
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.
I was wondering why we need string casts for exprs at all, because array key string which causes an conversion to integer is a
LNumberand should be skipped byThe culprit was LNumber with UnaryMinus:smile: