Chris Morgan
›
Git
›
anymap
› blobdiff
summary
|
shortlog
|
log
|
commit
|
commitdiff
|
tree
raw
|
inline
| side by side
commit
grep
author
committer
pickaxe
?
search:
re
Rename UncheckedAnyExt, fix Extend, tweak things
[anymap]
/
CHANGELOG.md
diff --git
a/CHANGELOG.md
b/CHANGELOG.md
index 7f76440407d83a5525114550cb124bf0688121e9..8dd437eee0e7ac2c298a7708c5ea86bdc32a3066 100644
(file)
--- a/
CHANGELOG.md
+++ b/
CHANGELOG.md
@@
-1,5
+1,14
@@
# 1.0.0 (unreleased)
# 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.2 (unreleased)
+
+- Fixed the broken `Extend` implementation added in 1.0.0-beta.1.
+
+# 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.
@@
-38,9
+47,6
@@
- 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)