Replace "cfg(test)" with "cfg(doctest)" for readme testing #761
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! bors r+ |
taiki-e
reviewed
May 21, 2020
bors bot
added a commit
to taiki-e/cargo-hack
that referenced
this pull request
Dec 5, 2020
102: Add --version-range option r=taiki-e a=taiki-e Closes #93 > This may be useful for catching issues like BurntSushi/termcolor#35, rust-lang/regex#685, rayon-rs/rayon#761 (comment), rust-lang/rust-clippy#6324. ```text --version-range <START>..[END] Perform commands on a specified (inclusive) range of Rust versions. If the given range is unclosed, the latest stable compiler is treated as the upper bound. Note that ranges are always inclusive ranges. --version-step <NUM> Specify the version interval of --version-range. ``` Note: Ranges are always **inclusive** ranges. (`start..=end`) ```console $ cargo hack check --version-range 1.46..1.47 info: running `cargo +1.46 check` on cargo-hack (1/2) Finished dev [unoptimized + debuginfo] target(s) in 0.28s info: running `cargo +1.47 check` on cargo-hack (2/2) Finished dev [unoptimized + debuginfo] target(s) in 0.23s ``` If the given range is unclosed, the latest stable compiler is treated as the upper bound. ```console $ cargo hack check --version-range 1.46.. info: running `cargo +1.46 check` on cargo-hack (1/3) Finished dev [unoptimized + debuginfo] target(s) in 0.28s info: running `cargo +1.47 check` on cargo-hack (2/3) Finished dev [unoptimized + debuginfo] target(s) in 0.23s info: running `cargo +1.48 check` on cargo-hack (3/3) Finished dev [unoptimized + debuginfo] target(s) in 0.28 ``` You can also specify the version interval by using `--version-step`. (`(start..=end).step_by(step)`) ```console $ cargo hack check --version-range 1.45.. --version-step 2 info: running `cargo +1.45 check` on cargo-hack (1/2) Finished dev [unoptimized + debuginfo] target(s) in 0.29s info: running `cargo +1.47 check` on cargo-hack (2/2) Finished dev [unoptimized + debuginfo] target(s) in 0.25s ``` Co-authored-by: Taiki Endo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rustdoc now passes "doctest" when running in test mode.