Drake Tetreault
Drake Tetreault
I would like to use tokio in a game I am making to implement coroutines that can execute across multiple game ticks. The way I would like this to work...
I am building a HTTP server on top of tokio that needs to perform minimal memory allocations per client TCP connection, regardless of how many HTTP requests are received through...
Adds a new feature `single-thread` which when activated removes the `#[thread_local]` dependency. The catch is that the user must guarantee that futures will never be polled from more than one...
Right now documentation is placeholder, need to update. Also consider hiding documentation for publish items in const_env_impl that are implementation details only exposed due to needing a separate impl crate...
Need to do a better job of reporting errors. Currently we just panic whenever we encounter a problem.