[WIP] atomic_sequence support: needs testing #127
Closed
Conversation
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
|
Bit of a note, though not adding any atomic functionality, using this rule: static constexpr auto rule(d, ctll::term<'>'>) -> ctll::push<reset_capture, ctll::anything, content_in_capture, ctll::term<'\x29'>>;Allows (?> syntax to be recognized as a sequence*, may be temporary patch. |
Andersama
force-pushed
the
atomic_group_nonunicode
branch
3 times, most recently
from
047fc2d to
9f17901
Compare
Andersama
changed the title
|
Roughly takes care of #108 |
Andersama
force-pushed
the
atomic_group_nonunicode
branch
2 times, most recently
from
ac4ab02 to
6983621
Compare
Still a work in progress...
Andersama
force-pushed
the
atomic_group_nonunicode
branch
from
6983621 to
d1b2fd4
Compare
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've likely butchered something here, but I think this is a rough idea to get atomic_sequence working.
Currently when trying to compile a regex w/ an atomic sequence I get errors about a missing apply function. So the LL1 parser / apply functions are a bit off.