NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io · #2815 most downloaded on crates.io
Futures-aware lock primitives
Last release 4 years ago
no release in 18 months
Release timing varies
gaps range from 9 days to 1.2 years
Nearly every release is documented
notes for 12 of 13 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
13 releases · first in 2018
(cargo-release) futures-locks version 0.7.1
(cargo-release) futures-locks version 0.7.1
(cargo-release) futures-locks version 0.7.0
(cargo-release) futures-locks version 0.7.0
Updated to Tokio 1.0. Crates needing Tokio 0.2 must stay on the 0.6 branch. (#42)
Mutex::try_lock, RwLock::try_read, and RwLock::try_write, now return a
dedicated error type instead of (), and it implements std::error::Error.
(#41)
RwLock: it shouldn't implement Sync unless
its inner type also does.
(#45)One column per quarter.
(cargo-release) futures-locks version 0.6.0
(cargo-release) futures-locks version 0.6.0
std::future. futures-locks no longer works with
futures-0.1. For futures-0.1-based applications, continue to use the 0.5
branch. Most methods have similar interfaces. However, the IntoFuture
trait no longer exists in the std::future world. And Future<T> doesn't
implement From<T> (though I don't know why it couldn't). So Mutex::with,
RwLock::with_read, and RwLock::with_write now take closures that return
impl Future, instead of impl IntoFuture. Closure arguments that used to
return something like Result<T, E> should now return
futures::future::ready<Result<T, E>> instead.(cargo-release) futures-locks version 0.5.0
(cargo-release) futures-locks version 0.5.0
Default for Mutex and RwLock
(#22)(cargo-release) version 0.4.0
(cargo-release) version 0.4.0
(cargo-release) version 0.3.3
(cargo-release) version 0.3.3
(cargo-release) version 0.3.2
(cargo-release) version 0.3.2
(cargo-release) version 0.3.1
(cargo-release) version 0.3.0
(cargo-release) version 0.3.0
Mutex::with_local, RwLock::with_read_local, and
RwLock::with_write_local for non-Send Futures.
(#7)Mutex::with, RwLock::with_read, and RwLock::with_write now require
their Futures to be Send. They also can return errors.
(#7)Mutex::with, RwLock::with_read, and RwLock::with_write now work with
all Tokio Runtimes.
(#7)(cargo-release) version 0.2.1
(cargo-release) version 0.2.1
Added methods for running critical code in its own task. These methods require Tokio.
Future for all future types, even when the wrapped type is
unsized.Futures should do nothing until polled.
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →