You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to get an understand of what if would take to port a crate like fancy-regex to use this "streaming regex" API? I would assume it would be high effort because that crate is based on regex, and it would have to be ported to the modified regex-automata API.
The text was updated successfully, but these errors were encountered:
My understanding is that that crate contains itw own regex engine/vm that only delegates to the regex crate in some cases.
Replacing the regex usage would probably be quite easy. The endgoal for this crate (it's not there yet) is to essentially offer the same APi as regex.
It should be possible to port that crates vm as well but it's hard to tell how much effort that would be. Probably a lot more ebut its likely reasoable. The VM doesn't look too complex. Ths would require an input that allow backwards iteration tough (for the backtracking). It should also likely be a separate project that would just depend on this crate (same relationship the original crate has to regex)
I wanted to get an understand of what if would take to port a crate like fancy-regex to use this "streaming regex" API? I would assume it would be high effort because that crate is based on regex, and it would have to be ported to the modified
regex-automata
API.The text was updated successfully, but these errors were encountered: