-
Notifications
You must be signed in to change notification settings - Fork 50
General ascii fast paths for character classes #644
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
Merged
Merged
Changes from 6 commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
bf06ee1
wip: General ASCII fast-paths for builtin character classes
milseman 88283b7
wip
milseman 38cf10e
wip: shorter
milseman 21b0b42
Add programmers manual
milseman 9aca045
unify code paths
milseman cf8fd52
fix for scalar semantic cr-lf
milseman c35b846
refactor and reorganize
milseman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# Programmer's Manual | ||
|
||
## Programming patterns | ||
|
||
### Engine quick checks and fast paths | ||
|
||
In the engine nomenclature, a quick-check results in a yes/no/maybe while a thorough check always results in a definite answer. | ||
|
||
The nature of quick checks and fast paths is that they bifurcate testing coverage. One easy way to prevent this in simple cases is to assert that a definite quick result matches the thorough result. | ||
|
||
One example of this pattern is matching against a builtin character class. The engine has a `_matchBuiltinCC` | ||
|
||
```swift | ||
func _matchBuiltinCC(...) -> Input.Index? { | ||
// Calls _quickMatchBuiltinCC, if that gives a definite result | ||
// asserts that it is the same as the result of | ||
// _thoroughMatchBuiltinCC and returns it. Otherwise returns the | ||
// result of _thoroughMatchBuiltinCC | ||
} | ||
|
||
@inline(__always) | ||
func _quickMatchBuiltinCC(...) -> QuickResult<Input.Index?> | ||
|
||
@inline(never) | ||
func _thoroughMatchBuiltinCC(...) -> Input.Index? | ||
``` | ||
|
||
The thorough check is never inlined, as it is a lot of cold code. Note that quick and thorough functions should be pure, that is they shouldn't update processor state. | ||
|
||
|
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
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.
[Future] It would be great if we had a macro to expand into this pattern, since we have to essentially repeat the same function call three times. Something like:
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.
Yes, that would be nice. When I did the string re-gutting, I had some (always-inline) functions that took two different closures and applied this kind of pattern, but it turned too unwieldy and for the UTF-8 switch it ended up being better to just stamp the code out manually. A macro would be ideal here.