Not 1.0.0 after all, but let’s call it 1.0.0-beta.1 rather than 0.13.0.
+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.
- Removed `anymap::any::Any` in favour of just plain `core::any::Any`, since its
`Send`/`Sync` story is now long stable.
- 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.
- 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)
# 0.12.1 (2017-01-20)
- Remove superfluous Clone bound on Entry methods (#26)
[package]
name = "anymap"
[package]
name = "anymap"
+version = "1.0.0-beta.1"
authors = ["Chris Morgan <rust@chrismorgan.info>"]
edition = "2018"
rust-version = "1.36"
authors = ["Chris Morgan <rust@chrismorgan.info>"]
edition = "2018"
rust-version = "1.36"