Carlos O'Ryan
Carlos O'Ryan
Thanks for the offer. I do not think this is a good issue for an external contributor, we are not even sure if we want to change the w1r3 benchmark...
And I did change my mind. The random access benchmark is good enough for our purposes.
@PhongChuong are you still working on this? It is fine if you are not.
Should we add this to the stabilization milestone? At least one of the solutions seems to change the API, and it is not clear if the change is breaking?
As discussed today, fixing this would just require adding some new functions, it would not be a breaking change.
Can we close this? The examples are gone.
I think this is in the 0.13.1 release, so it is no longer blocked.
> Excited to have an official Rust SDK, so thanks! We are too. > > I'm trying to figure out how to use the `CacheableResource` type in google-cloud-auth and have...
> I've been using, but been quite nervous about, using `unreachable!()` for this code path. Could you also add some explicit clarification/guarantees on under what conditions a `NotModified` won't be...
> Cons: Introduces runtime overhead due to locking. Accessing extensions requires handling the MutexGuard's lifetime, and calls can panic if the mutex is poisoned. Also introduces runtime overhead because creating...