Adds support for swift regexes#37
Open
beelsebob wants to merge 2 commits into
Open
Conversation
Adds support for swift regular expressions. Does make an API change - the regex option in the LexingRule class is renamed to nsRegex, and regex is taken over by the swift regex. This is because I couldn’t come up with a good name for “not foundation regex”.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
does make an API change though...
.regex now accepts a native swift regex, while .nsRegex is added for the old Foundation regex option. This is because I couldn't come up with a good name for the native regex case. If you have a preferred option to not change the API, I'd happily change the name.