X-Git-Url: https://git.chrismorgan.info/anymap/blobdiff_plain/8ebb2d7e04d86d09614f578342e4765276372e7b..0a1c85f8655a71b995d228ed0c9496f732268c5b:/CHANGELOG.md

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 04b57ee..214ba6b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,13 +1,34 @@
 # 1.0.0 (unreleased)
 
+- Removed `anymap::any::Any` in favour of just plain `core::any::Any`, since its
+  `Send`/`Sync` story is now long stable.
+
+  - This loses `Any + Sync`. `CloneAny + Sync` is also removed for consistency.
+    (So `Any + Sync` is gone, but `Any`, `Any + Send` and `Any + Send + Sync`
+    remain, plus the same set for `CloneAny`.)
+
+- `anymap::any::CloneAny` moved to `anymap::CloneAny`.
+  With nothing public left in `anymap::any`, it is removed.
+
 - Relicensed from MIT/Apache-2.0 to BlueOak-1.0.0/MIT/Apache-2.0.
 
-- Remove `bench` Cargo feature (by shifting benchmarks out of `src/lib.rs` into
-  `benches/bench.rs`; it still won’t run on anything but nightly, but that
-  don’t signify). Technically a [breaking-change], but it was something for
-  development only, so I’m not in the slightest bit concerned by it.
+- Increased the minimum supported version of Rust from 1.7.0 to 1.36.0.
+
+- no_std is now possible in the usual way (default Cargo feature 'std'),
+  depending on alloc and hashbrown.
+
+- Removed the `bench` Cargo feature which was mostly to work around historical
+  Cargo limitations, but was solved by moving benchmarks from `src/lib.rs` to
+  `benches/bench.rs` even before those limitations were lifted. The benchmarks
+  still won’t run on anything but nightly, but that don’t signify.
+
+- Implemented `Default` on `Map` (not just on `RawMap`).
+
+- The implementation of `Into<RawMap<A>>` for `Map<A>` has been
+  replaced with the more general `From<Map<A>>` for `RawMap<A>`.
 
-- Implement `Default` on `Map` (not just on `RawMap`)
+- Worked around the spurious `where_clauses_object_safety` future-compatibility lint that has been raised since mid-2018.
+  If you put `#![allow(where_clauses_object_safety)]` on your binary crates for this reason, you can remove it.
 
 I don’t plan for there to be any real changes from 0.12.1;
 it should be just a bit of housecleaning and a version bump.