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

[Closes #236] Operator space false positive #259

Merged
merged 8 commits into from
Aug 27, 2015

Conversation

jfacorro
Copy link
Contributor

{string, _} -> [];
{char, _} -> [];
{comment, _} -> [];
{_, string} -> [];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why matching all this cases? If I'm not mistaken it would either be undefined or any of your valid options. Wouldn't matching undefined and have an otherwise default behaviour save lines?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have to check for those types of nodes or tokens where an operator without a space is acceptable. An alternative would be to match for all that shouldn't have it, but in either case there needs to be an explicit specification of the valid (or invalid) types of nodes/tokens.

HernanRivasAcosta added a commit that referenced this pull request Aug 27, 2015
…positive

[Closes #236] Operator space false positive
@HernanRivasAcosta HernanRivasAcosta merged commit e316259 into master Aug 27, 2015
@jfacorro jfacorro deleted the jfacorro.236.operator_space_false_positive branch August 27, 2015 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants