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
The push-oriented implementation of Aho-Corasick returns an iterator over the matches it finds. The public regex API instead reports matches via callbacks. I'd like to see the public API also return an iterator.
Something like:
for match in scratch.push(bytes){// do things}
A big question is how to handle scratch.finish, which consumes the scratch but also might return matches.
The text was updated successfully, but these errors were encountered:
that could be handled using Iterator::collect. the only difference being that it would be possible to get a collection with 0 elements if there are no stored matches in the instance. I admit I haven't seen much of how this library works, but I'm throwing this idea out there.
The push-oriented implementation of Aho-Corasick returns an iterator over the matches it finds. The public regex API instead reports matches via callbacks. I'd like to see the public API also return an iterator.
Something like:
A big question is how to handle
scratch.finish
, which consumes the scratch but also might return matches.The text was updated successfully, but these errors were encountered: