Ryan Leckey

I really love the idea of a default, thread-local Core. --- I have a (somewhat) novel addition though. - Add a `Drop` impl to Future that would schedule the future...

I'd say that is very unintuitive and doesn't seem to be documented anywhere (but I may have missed it). No, I think I understand what you meant. It doesn't cancel...

@alexcrichton I guess I'm just having a disconnect from coming from a land of eager futures vs lazy futures. I can see that there is a is a strong advantage...

This might be a bit radical but I believe we should name `failure`s error type, `error`. 🌏 I imagine a world where Rust has a primitive error type, named `error`...

I see `failure` as forever providing: - Error derives. Library authors will want custom error types and helping to make this use case simple is a good but polarizing goal...

I like the per-provider idea. I don't even see the need for this to be user-configurable (it could still be of course). I don't want html to be auto-completed in...

Is there anything needed here before this is merged? I'd really love to see this merged and support added to cupertino_http.

```rust #[allow(non_camel_case_types)] struct __shio_route_hello { } impl Clone for __shio_route_hello { fn clone(&self) -> Self { *self } } impl Copy for __shio_route_hello { } #[allow(non_upper_case_globals)] static hello: __shio_route_hello =...

@Meralis40 Over all, nice work! Let's get this cleaned up a bit and we can merge it in. I'd love to see the "standard" methods before this is released though:...

It'd make the most sense in a `context/builder.rs` file I'd think. Going by the Rust API guidelines it should probably be named `shio::context::Builder`. We should also have a `Context::builder(handle)` or...