Fix issue278: Return an object literal #280
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
Parser: Allow objectLiterals as returnStatement values.
Require objectLiterals to be empty brackets or have a colon-delimited
declared value.
Add a few new unit tests for return statements.
|
@sganapavarapu1, @as3boyan, Can one of you please review this? The only real change in this code is to haxe.bnf. Everything else is generated code or a test (which can certainly bear reviewing, but it's not critical). |
|
Should be fine |
EBatTiVo
added a commit
that referenced
this pull request
May 27, 2015
Fix issue278: Return an object literal
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.
Parser: Allow objectLiterals as returnStatement values.
Require objectLiterals to be empty brackets or have a colon-delimited
declared value.
Add a few new unit tests for return statements.