Add support for async/non-blocking about aho-corasick HOT 7 CLOSED

The Read trait supports that.

I will not be adding async support without a very compelling and detailed justification for it. If you can provide that, we can reopen this issue.

from aho-corasick.

If I wanted to do something like:

let in: &[u8] = ...;
let out: &[u8] = replacer.feed(in);

How can this be done with the current interface?
Note that replacer was pre-existing, so might be in a non-initial state (not trying to feed all of the input at once).

from aho-corasick.

You haven't described your problem in enough detail for me to be able to answer you.

async seems like a red herring.

It sounds like you want a push API, but this crate only exposes a pull API. If you want a push API you'll probably need to build it yourself using regex-automata.

from aho-corasick.

I’m fine with push or pull, just don’t want to have a thread/stack allocated for each long-running replacer.

Use-case is streaming log filtering.

from aho-corasick.

Like I said, I don't see this happening without a very detailed investigation. This crate is primarily about text search, which is a CPU bound operation. There's only a tiny little sliver of API that has anything to do with I/O, and that's a convenience function for searching std::io::Read because it's a low hanging fruit.

from aho-corasick.

I would rather work to expose APIs that permit callers to implement any necessary I/O glue instead of providing it in this crate.

from aho-corasick.

I’m not asking for Tokio/futures Streams/… support, to be clear. Fine with any API that allows me to write the glue.

Maybe this API aready exists, I just don’t have the imagination how to make it work short of allocating a dedicated thread. Pull is fine, but then needs O_NONBLOCK :)

Rephrased differently, I’d like to get the internal state somewhere else than on the stack if possible, so I can resume later.

Thanks for the pointer to regex-automata!

from aho-corasick.