Regex lookbehind implementation decission #1330
Unanswered
MaxSagebaum
asked this question in
Q&A
Replies: 1 comment
-
As this project is aimed at showcasing what's possible in terms of unifying/generalizing C++ concepts and offering a simple UX to them, I strongly prefer your option 2. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello @ all,
I am currently implementing the missing regex lookbehind functionality. In this context I need to transform the iterators into reverse iterators, and the match context into a reverse match context.
The problem I have is the following: Currently, the function generation is strongly typed for the iterator (
Iter
) and the context. I have now two ways to go:reverse
generation. It would be some additional ifs that prepend aReverse
in front of the iterator type and the context type. This would increase code complexity for the generator and add kind of a statement machine. (Reverse generation on/off).My previous tests showed that the template engine is not the bottleneck in the code generation. It is the optimizer. So compilation times would probably stay the same.
Currently, I am leaning to 2). Any thoughts?
Beta Was this translation helpful? Give feedback.
All reactions