-
Notifications
You must be signed in to change notification settings - Fork 49
Persist persistent state in the processor. #773
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
Conversation
Fixes #770 |
@swift-ci please test |
Most of those perf swings (including regressions) are from refactoring the interface itself. Refactoring-only:
New iteration model vs post-refactoring:
|
@swift-ci please test |
1 similar comment
@swift-ci please test |
subjectBounds: Range<String.Index>, | ||
searchBounds: Range<String.Index> | ||
) -> Matches { | ||
fatalError() |
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.
Is this method superfluous now? I don't see it called anywhere…
// subjectBounds: subjectBounds, | ||
// searchBounds: searchBounds, | ||
// graphemeSemantic: graphemeSemantic) | ||
// } |
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.
Can we remove these leftovers?
@swift-ci Please test |
@swift-ci please test |
1 similar comment
@swift-ci please test |
rdar://137607522 |
04fc821
to
e67f4c7
Compare
Refactor executor interfaces as well
e67f4c7
to
c7c7b48
Compare
@swift-ci test |
@swift-ci please test macOS platform |
Refactor executor interfaces as well
New benchmark: word boundaries in urls