Feature: RwLock

[svenknobloch]

Are there any current plans to add a future-aware RwLock to complement the Mutex?

I would be happy to try my hand at an implementation based on the current mutex implementation but would need some input as to the desired reader/writer fairness policy.

[yoshuawuyts]

async_std::sync::RwLock might serve as a useful reference impl.

[d-e-s-o]

Would be great to have such functionality.

[rj-calvin]

@yoshuawuyts I've looked at their implementation, I think it already shares a number of similarities with futures::lock::Mutex considering that they both use a similar setup for maintaining wakers. The difference is that async_std defines a separate type called WakerSet.

[xpepermint]

Is there a release milestone?

[ghost]

@xpepermint You can use https://github.com/stjepang/async-rwlock until a RwLock is added to futures.

[xpepermint]

I see. Thank you @stjepang

[Enrico2]

@stjepang Hi, I see that repository no longer exists or is no longer public?

Does anyone know what's the current status of this issue? Thanks.

[Enrico2]

Oh I see it's at https://github.com/stjepang/async-lock

[rj-calvin]

@xpepermint @Enrico2 Sorry for the egregious delay. I have a PR (#2082) that is available though I haven't yet gotten any sort of go ahead with its current state. I believe the code should function, in theory, identically to the one provided in https://github.com/stjepang/async-lock.