Replies: 1 comment 2 replies
-
Yeah like I was saying in chat, this approach doesn't work in the current or future architecture. It doesn't work in the current one because this only applies to one of the three NFAs compiled. And in the future architecture, it won't apply to any of the NFAs it compiles because the ability to match on |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I ran into an issue with the unicode
\w
using a lot of memory because it contains many char ranges. This becomes worse with repetition expansion as the entire class is repeated. After a couple hours of messing around I've come up with a pretty simple solution, simply adding a special instruction for\w
(master...devsnek:regex:specialization). This code is very mess as I was just experimenting, but I am curious how folks feel about this approach and whether it should be used in this crate. I also know that @BurntSushi is working on rewrites of some internals, so I would want to wait for that before implementing this I think.Beta Was this translation helpful? Give feedback.
All reactions