fix: tokenize alphanumeric strings correctly #52
Merged
Conversation
This file contains 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
|
That makes sense, thanks; can you just fix the one formatting nit and rebase (I fixed the new |
AgentElement
force-pushed
the
alphanumeric-fix
branch
from
9f192bf to
e10c296
Compare
|
Should now be done, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bound variable names in abstractions that contained numbers did not parse correctly. For example,
\x1. xwould not tokenize because of thex1under abstraction, but\x. x1would. This commit allows any alphanumeric string not beginning with a number to be used as the name for a bound variable.