-
Notifications
You must be signed in to change notification settings - Fork 22
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
Tokenize purely using regexes #123
Tokenize purely using regexes #123
Conversation
a492556
to
056670d
Compare
3a81fb4
to
1a8dc67
Compare
1a8dc67
to
9ed8bdb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Impressive work, thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like at least 2 commits could be squashed together
+7% speedup
9ed8bdb
to
808c095
Compare
last 3 commits squashed (3rd commit was reverting 1st commit, therefore the resulting/last commit is very simple) |
Thank you. |
Match next token using single regex only, +18% speedup.
In the future,
Tokenizer::makeTokenizeRegexes()
method can be made public to allow grammar override for each token type.