Lucio Franco
Lucio Franco
I think this makes a lot of sense. I believe most of the features we are waiting on are almost ready (and should be on nightly). My main question though...
I'd like to add another note https://github.com/awslabs/smithy-rs/ is a pretty big consumer of tower so we should also consider their use. > Hmm, what language features are you thinking about...
Right, my point is we should use hypers timeline to ensure that we 1.0 for inclusion into hypers 1.0 release. I think it would be pretty important ecosystem wise to...
Token types should allow call to take `&self` and would then allow us to migrate to `async fn` in traits, though I believe the required features for all of that...
I agree that this API is much more misuse resistant and would enable disarm. That said, I think as of now none of us have the current bandwidth to refactor...
I think the plan for the next breaking change for `tower-service` is planned for when GAT arrives. cc @carllerche id love to hear your thoughts
Thanks for the write-up @jonhoo! So I think for now Option C and D are kind of off the table until we see this is actually causing issues. So far...
@seanmonstar I would imagine this error should be returned via the call, not via poll_ready?
This seems quite reasonable. I am curious if you could explain the zerbra and your use case? also @jonhoo has done a lot of work on the buffer, I am...
@lovesegfault yeah, good idea, this seems like a config option that could live in `HttpRetry`.