Lucio Franco
Lucio Franco
@Yneth maybe it makes sense to use ready as a signal that the data is ready then use global getters that return an `Option`. Could maybe use something like a...
Would also be good to get CI to run against this change which may just need a new commit to trigger it.
I got to a similar spot ```rust #![feature(type_alias_impl_trait)] use std::future::Future; pub trait Service { type Res; type Err; type Future(&'a self, req: Req) -> Self::Future
FYI I am doing some work w/ async_fn in traits feature on nightly. Will eventually report back but since that feature is landing much sooner than I thought I think...
@leoyvens correct, I've already communicated this to the async wg.
Yeah, feel free to open a PR, not sure how big the refactor is gonna be tho.
> That comment was prompted as I wondered about the cost of including all the static strings in the binary, when certainly most applications will never need them. Do we...
Ok I have a fix here for it https://github.com/hyperium/tonic/pull/1315 feel free to review it.
This now exists via https://github.com/hyperium/tonic/pull/1472
Its likely an issue with ghz and not tonic.