# 1.0.0 (unreleased)
+Planned once the dust of 1.0.0-beta.1 settles, since 1.0.0-beta.1 ended up
+being bigger than I’d earlier intended.
+
+# 1.0.0-beta.1 (2022-01-25)
+
- Removed `anymap::any::Any` in favour of just plain `core::any::Any`, since its
`Send`/`Sync` story is now long stable.
- 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>`.
+- Added `Entry::{or_default, and_modify}` (std::collections::hash_map parity).
+
+- Removed the `anymap::raw` wrapper layer around `std::collections::hash_map`,
+ in favour of exposing the raw `HashMap` directly. I think there was a reason
+ I did it that seven years ago, but I think that reason may have dissolved by
+ now, and I can’t think of it and I don’t like the particular safe
+ `as_mut`/unsafe insert approach that I used. Because of the hashbrown stuff,
+ I have retained `anymap::RawMap` is an alias, and `anymap::raw_hash_map` too.
+ The end result of this is that raw access can finally access things that have
+ stabilised since Rust 1.7.0, and we’ll no longer need to play catch-up.
- 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.
-
# 0.12.1 (2017-01-20)
- Remove superfluous Clone bound on Entry methods (#26)