Skip to content

Add missing symbolic operator characters. Remove non-keywords. #42

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

Merged
merged 2 commits into from
Aug 4, 2017

Conversation

trepidacious
Copy link
Contributor

Symbolic operators can contain & and =, so add these to relevant
regexes.
Fix typo on "Capitol".
Comparison, logical and arithmetic "keywords" are actually just methods
in scala, so remove these. They also caused problems by matching
against parts of other methods, like ===.
Add new match for assignment with =, making sure this doesn't match
symbolic operators containing = character.
Make sure that operators like <-, => don't match against symbolic
operators containing them as a substring.

Symbolic operators can contain `&` and `=`, so add these to relevant
regexes.
Fix typo on "Capitol".
Comparison, logical and arithmetic "keywords" are actually just methods
in scala, so remove these. They also caused problems by matching
against parts of other methods, like `===`.
Add new match for assignment with `=`, making sure this doesn't match
symbolic operators containing = character.
Make sure that operators like `<-`, `=>` don't match against symbolic
operators containing them as a substring.
@laughedelic
Copy link

@trepidacious could you update this pull-request?

@trepidacious
Copy link
Contributor Author

No problem, I think that does it - I've just brought across the changes from a-zA-Z to \p{L} and similar, so the original description should still cover what this does :)

@laughedelic
Copy link

Thanks! Hopefully somebody will review it soon and merge.
@50Wliu, @gangstead? I don't really understand who's in charge here..

@gangstead gangstead merged commit e804377 into atom-community:master Aug 4, 2017
@gangstead
Copy link
Contributor

I'm not really sure either. I transferred the package to /atom-community/ because I wasn't really active in maintaining it anymore and so I guess anyone who is an owner there can merge in things and publish new versions.

It's not clear what the process is to become a new owner.

@gangstead
Copy link
Contributor

published in [email protected]

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