This library assumes `async-std`; the way it parallelizes work is by spawning tasks on an executor, so by design it needs to have access to one. Without that we

This library assumes `async-std`; the way it parallelizes work is by spawning tasks on an executor, so by design it needs to have access to one. Without that we couldn't provide the API we do. I haven't tested it with `hyper`, but it should soon be compatible with `tide`(assuming `async-h1/async-std` is used as the backend).