alex/anymap
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

1.0.0-beta.2

Browse source
This commit is contained in:
Chris Morgan 2022-02-22 13:54:20 +11:00
parent 40e60cefd6
commit 2e9a570491
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Cargo.toml
View file

@ -1,6 +1,6 @@
[package]
name = "anymap"
version = "1.0.0-beta.1"
version = "1.0.0-beta.2"
authors = ["Chris Morgan <rust@chrismorgan.info>"]
edition = "2018"
rust-version = "1.36"

4
README.md
View file

@ -45,14 +45,14 @@ Typical Cargo.toml usage, providing `anymap::AnyMap` *et al.* backed by `std::co
```toml
[dependencies]
anymap = "1.0.0-beta.1"
anymap = "1.0.0-beta.2"
```
No-std usage, providing `anymap::hashbrown::AnyMap` *et al.* (note the different path, required because Cargo features are additive) backed by `alloc` and the [hashbrown](https://rust-lang.github.io/hashbrown) crate:
```toml
[dependencies]
anymap = { version = "1.0.0-beta.1", default-features = false, features = ["hashbrown"] }
anymap = { version = "1.0.0-beta.2", default-features = false, features = ["hashbrown"] }
```
**On stability:** hashbrown is still pre-1.0.0 and experiencing breaking changes. Because it’s useful for a small fraction of users, I am retaining it, but with *different compatibility guarantees to the typical SemVer ones*. Where possible, I will just widen the range for new releases of hashbrown, but if an incompatible change occurs, I may drop support for older versions of hashbrown with a bump to the *minor* part of the anymap version number (e.g. 1.1.0, 1.2.0). Iff you’re using this feature, this is cause to *consider* using a tilde requirement like `"~1.0"` (or spell it out as `>=1, <1.1`).