You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would it be possible to expose BiLock in a way that follows semver, even if it is separate from the normal future crates? I don't even mind if it updates extremely often, but as it is now it's not really possible for a library to depend on BiLock since it would mean the library itself does not follow semver, or would possibly require an exact bound on futures-util.
I suppose you could make the same argument about the other unstable features as well so I understand if this is too much of a headache to bother with. I'd really like to use BiLock in a library though, as I'm not aware of another way to provide a poll style interface on top of something that needs to share a futures-aware mutex.
The text was updated successfully, but these errors were encountered:
Would it be possible to expose
BiLock
in a way that follows semver, even if it is separate from the normal future crates? I don't even mind if it updates extremely often, but as it is now it's not really possible for a library to depend onBiLock
since it would mean the library itself does not follow semver, or would possibly require an exact bound onfutures-util
.I suppose you could make the same argument about the other unstable features as well so I understand if this is too much of a headache to bother with. I'd really like to use
BiLock
in a library though, as I'm not aware of another way to provide a poll style interface on top of something that needs to share a futures-aware mutex.The text was updated successfully, but these errors were encountered: