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.

Sign up for GitHub

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

Jump to bottom

Lexer performance boost by inspecting the first character #682

Merged
merged 1 commit into from
Apr 13, 2018
Merged

Lexer performance boost by inspecting the first character #682

merged 1 commit into from
Apr 13, 2018

Conversation

bd82
Copy link
Member

@bd82 bd82 commented Mar 18, 2018

of the "next input" to filter the possible patterns that need be examined.

@coveralls
Copy link

coveralls commented Mar 18, 2018 •
edited
Loading

Coverage Status

Coverage remained the same at 100.0% when pulling 32003c0 on lexer_optimize into ff61de8 on master.

@bd82 bd82 force-pushed the lexer_optimize branch 3 times, most recently from 034aed8 to 6b216b0 Compare March 18, 2018 23:52
@bd82 bd82 force-pushed the lexer_optimize branch 11 times, most recently from 609e8ba to 32003c0 Compare April 13, 2018 15:50
@bd82
Lexer performance boost by inspecting the first character
32003c0 
of the "next input" to filter the possible patterns that need be examined.
@bd82
Copy link
Member Author

bd82 commented Apr 13, 2018

This fixes #679

@bd82 bd82 merged commit bceab62 into master Apr 13, 2018
@bd82 bd82 mentioned this pull request Apr 14, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@bd82 @coveralls