Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

matchedDotOperatorCallOperation #114

Merged
merged 8 commits into from
Apr 20, 2015

Conversation

KronicDeth
Copy link
Owner

The matchedDotOperatorCallOperation rule implements the operator portion of #30. A subrule is noParenthesesOneArgument which implements part of #60, but not it's direct usage in matchedExpression as noParenthesesOneArgument is treated as an argument itself in matchedDotOperatorCallOperation (Alias.|> function argument).

Verification Steps

  • VERIFY org.elixir_lang tests run locally
  • VERIFY travis-ci build passes.

@KronicDeth KronicDeth self-assigned this Apr 20, 2015
@KronicDeth KronicDeth added this to the v1.0.0 milestone Apr 20, 2015
@KronicDeth KronicDeth mentioned this pull request Apr 20, 2015
Closed
11 tasks
@KronicDeth KronicDeth merged commit 2f0f0d8 into master Apr 20, 2015
KronicDeth added a commit that referenced this pull request Apr 20, 2015
@KronicDeth KronicDeth deleted the feature/30/matched-dot-operator-call-operation branch April 20, 2015 02:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant