0a1c85f865
I’m quite pleased with how this has turned out. Given the stability-despite-instability of hashbrown (that the API surface we’re depending on hasn’t changed since 0.1.1), and the deliberate altered SemVer guarantees for it, it was very tempting to leave the hashbrown range open, `version = ">=0.1.1"` or at least `version = ">=0.1.1, <1"`, but for some reason or other I ended up deciding not to. I’m still of two minds about it, really.
21 lines
816 B
TOML
21 lines
816 B
TOML
[package]
|
|
name = "anymap"
|
|
version = "0.12.1"
|
|
authors = ["Chris Morgan <rust@chrismorgan.info>"]
|
|
edition = "2018"
|
|
rust-version = "1.36"
|
|
description = "A safe and convenient store for one value of each type"
|
|
repository = "https://github.com/chris-morgan/anymap"
|
|
keywords = ["container", "any", "map"]
|
|
categories = ["rust-patterns", "data-structures", "no-std"]
|
|
license = "BlueOak-1.0.0 OR MIT OR Apache-2.0"
|
|
include = ["/README.md", "/COPYING", "/CHANGELOG.md", "/src"]
|
|
|
|
[features]
|
|
default = ["std"]
|
|
std = []
|
|
|
|
[dependencies]
|
|
# The hashbrown feature, disabled by default, is exposed under different stability guarantees than the usual SemVer ones: by preference the version range will only be extended, but it may be shrunk in a MINOR release. See README.md.
|
|
hashbrown = { version = ">=0.1.1, <0.13", optional = true }
|