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

Make sure operators ending in alphanumerics also have a word boundary after them #457

Merged
3 commits merged into from
Feb 6, 2019

Conversation

masak
Copy link
Owner

@masak masak commented Feb 6, 2019

Ended up doing not just prefixes (as #408 discusses), but also infixes and postfixes, which suffer from the same problem.

Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

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

I don't know if I get this right, but the error msgs constitute a great improvement. I really think that precise error msgs are important. And at least earlier, the error msgs (I know that this has not been a priority) was frustrating from time to time. I can't of course not say anything about the code quality :)

@ghost ghost merged commit ce059b4 into master Feb 6, 2019
@masak masak deleted the masak/op-boundaries branch February 7, 2019 01:00
@masak
Copy link
Owner Author

masak commented Feb 7, 2019

Thanks!

Just to set the record straight, this PR introduces new parse errors here and there, but there are no new error messages or error types — agreed that the whole error message system needs an overhaul. Most likely this will be somewhat improved via #245 in the near future.

masak pushed a commit to masak/007-conscious-risks that referenced this pull request Feb 7, 2019
Thus `H25` becomes `H 25`, etc. This is necessary to track the
change introduced in masak/alma#457 --
with this fix, the game works again.
This pull request was closed.
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.

1 participant