fixed compiler crash when unable to determine signature of function…#321
Merged
fixed compiler crash when unable to determine signature of function…#321
Conversation
…rgument when passing a function expression
Perryvw
approved these changes
Jan 6, 2019
tomblind
added a commit
that referenced
this pull request
Jan 9, 2019
* fixed compiler crash when unable to determine signature of function… (#321) * fixed compiler crash when unable to determine signature of function argument when passing a function expression * added test * Validation crash fix (#326) * fix for crash when validating assignments of arrays/tuples * added re-assignment code to tuple return test * added new tuple assignment test and fixed others * changed static methods and lambda-properties to take a context parameter by default (#322)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
…argument when passing a function expression
Cases like this:
would cause the compiler to crash when trying to deduce if the passed function expression should have context or not. Now this will fail gracefully and the expression will be assumed to be a non-method.