futures-locks

(cargo-release) futures-locks version 0.7.1

• The published package on crates.io now includes functional tests. No user-visible changes. (#53)

(cargo-release) futures-locks version 0.7.0

Added

Changed

• 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)

Fixed

• Fixed a soundness issue with RwLock: it shouldn't implement Sync unless its inner type also does. (#45)

Removed

(cargo-release) futures-locks version 0.6.0

Added

Changed

• Updated to 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.

Fixed

Removed

(cargo-release) futures-locks version 0.5.0

Added

• Derived Default for Mutex and RwLock (#22)

Changed

• Minimum compiler version has increased to 1.32.0 (#28)

Fixed

• Fixed panics after an unready Future gets dropped (#24)

(cargo-release) version 0.4.0

Added

• Added Mutex::ptr_eq() (#20)
• Added MutexWeak (#17)

(cargo-release) version 0.3.3

(cargo-release) version 0.3.2

Changed

• Better documentation (#15)

(cargo-release) version 0.3.1

Changed

• Minimum compiler version has increased to 1.31.0 (#10)
• futures-locks only depends on tokio crates tokio-current-thread and tokio-executor when built with the tokio feature. (#10)

(cargo-release) version 0.3.0

Added

• Added Mutex::with_local, RwLock::with_read_local, and RwLock::with_write_local for non-Send Futures. (#7)

Changed

• Mutex::with, RwLock::with_read, and RwLock::with_write now require their Futures to be Send. They also can return errors. (#7)
• Methods enabled with the tokio feature now return a Future type equivalent to the one returned by the provided closure. (#6)

Fixed

• Mutex::with, RwLock::with_read, and RwLock::with_write now work with all Tokio Runtimes. (#7)

(cargo-release) version 0.2.1

Changed

• Tokio support is now enabled by default.

Added

• Added methods for running critical code in its own task. These methods require Tokio. (#3)
• Implemented Future for all future types, even when the wrapped type is unsized.

Added

Changed

• Futures should do nothing until polled. (#2)
• Fixed potential deadlocks when dropping Futures without first polling them. (#1)

Fixed

Removed