TNFA #4
Closed
TNFA #4
Conversation
This file contains 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 was implemented in nim-regex0 and it's too much work to port here. Moreso if the end goal is a TDFA (one day). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I copied nim-regex code and tweaked the
nfamatch2to make the sub-matches take O(M*C) space, where M is the length of the regex and C the number of capture groups.Well, it actually takes unbounded space because I didn't bother to reuse the parallel sub-matches, a new one is created every time a capture is found instead :P. This is just a PoC showing the idea works.
The next step is to make a DFA with some of the TDFA ideas.