This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
Add support for unary + in mapping keys (0.4.x. compatibility) #2097
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 allows mapping keys that begin with a unary
+to work. Unary+isn't legal anymore, but it was legal prior to 0.4.18.As you may recall, our system for recording mapping keys doesn't work if the outermost operation in the index expression is (on the bytecode level) a no-op. Obviously, that includes unary
+. I didn't account for this earlier because I didn't realize it was legal in old versions. Well, it is, so I've accounted for it, in the same way I've accounted for other no-ops.