Operators and call expressions #1946
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
This changes what can.compute.read takes to include info about how the property should be read. This changes scope to deal with it. This adds a basic Helper expression that seems to work like the old helper expression. This adds a better expression parser. I need to hookup the new expressions in place of the old expressions and make sure expression.Call works as well as the new operators.
…uld be a release canidate
justinbmeyer
added a commit
that referenced
this pull request
Sep 25, 2015
Operators and call expressions
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.
For #1699 and #1700. This needs docs. Uses
{child}=scope,child}=scope, andchild{=scopefor bindings.