-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: adding shellstyle patterns can burn time and memory #67
Comments
Sounds like a good candidate to add some |
Yes on fuzzing. Ouch, this one is really beating me up, we may end up running into a fundamental computer-science issue here and just say that combining a lot of wildcards makes AddPattern() expensive in both time and memory. But haven't given up yet. |
Fair enough Tim, there‘s always a cost and at least if users are aware of penalties, IMHO that‘s fine for now. |
Closes: #67 Signed-off-by: Tim Bray <tbray@textuality.com>
If you add a sequence of random shellstyle patterns Quamina quickly starts generating huge automata and AddPattern starts slowing down dramatically to the point where it's basically unusable.
My test words that produced this effect: "aahed*", "aalii", "aargh", "aarti*", "abaca", "abaci", "aback", "abacs", "abaft", "abaka", "abamp", "aband", "abase", "abash", "abask", "abate", "abaya", "abbas", "abbed*", "ab*bes"
The text was updated successfully, but these errors were encountered: