anymap/.travis.yml

language: rust
rust:
  - 1.36.0
  - nightly
  - stable
script:
  - if [[ "$(rustc --version)" =~ -(dev|nightly) ]]; then cargo bench; fi
  - if [[ "$(rustc --version)" =~ 1.36.0 ]]; then cp test-oldest-Cargo.lock Cargo.lock; fi
  - cargo test
  - cargo test --release
  - cargo test --no-default-features --features hashbrown
  - cargo test --release --no-default-features --features hashbrown
Make Travis use its own Rust support and cargo. 2014-09-29 08:58:51 +10:00			`language: rust`
Rename 'nightly' feature to 'unstable'. 2015-06-10 08:59:47 +10:00			`rust:`
no_std support 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. 2022-01-25 21:24:48 +11:00			`- 1.36.0`
Rename 'nightly' feature to 'unstable'. 2015-06-10 08:59:47 +10:00			`- nightly`
Test Rust stable on Travis also. 2015-06-10 19:26:32 +10:00			`- stable`
Initial release. 2014-06-12 17:29:24 +10:00			`script:`
Remove the `bench` Cargo feature as superfluous A better pattern is to put benchmarks in the `benches` directory; that way, `cargo test` won’t pick them up by default, and so it won’t fail on the stable and beta channels. 2017-01-21 03:01:56 +11:00			`- if [[ "$(rustc --version)" =~ -(dev\|nightly) ]]; then cargo bench; fi`
no_std support 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. 2022-01-25 21:24:48 +11:00			`- if [[ "$(rustc --version)" =~ 1.36.0 ]]; then cp test-oldest-Cargo.lock Cargo.lock; fi`
0.10.3: Rust beta support This is accomplished at a certain loss of efficiency, sadly. Add the 'nightly' feature to get things back how they were. 2015-04-18 10:44:34 +10:00			`- cargo test`
Remove the `bench` Cargo feature as superfluous A better pattern is to put benchmarks in the `benches` directory; that way, `cargo test` won’t pick them up by default, and so it won’t fail on the stable and beta channels. 2017-01-21 03:01:56 +11:00			`- cargo test --release`
no_std support 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. 2022-01-25 21:24:48 +11:00			`- cargo test --no-default-features --features hashbrown`
			`- cargo test --release --no-default-features --features hashbrown`