rust/library/core/Cargo.toml

[package]
authors = ["The Rust Project Developers"]
name = "core"
version = "0.0.0"
autotests = false
autobenches = false
edition = "2018"

[lib]
test = false
bench = false

[[test]]
name = "coretests"
path = "tests/lib.rs"

[[bench]]
name = "corebenches"
path = "benches/lib.rs"
test = true

[dev-dependencies]
rand = "0.7"

[features]
# Make panics and failed asserts immediately abort without formatting any message
panic_immediate_abort = []
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 17:19:23 -06:00			`[package]`
			`authors = ["The Rust Project Developers"]`
			`name = "core"`
			`version = "0.0.0"`
Switch to 1.26 bootstrap compiler 2018-05-10 13:02:19 -05:00			`autotests = false`
			`autobenches = false`
libcore => 2018 2019-04-14 21:23:21 -05:00			`edition = "2018"`
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies. 2016-01-21 17:19:23 -06:00
			`[lib]`
			`test = false`
rustbuild: Point to core and collections's external benchmarks. 2016-11-25 15:13:59 -06:00			`bench = false`
rustbuild: Add support for crate tests + doctests This commit adds support to rustbuild to run crate unit tests (those defined by `#[test]`) as well as documentation tests. All tests are powered by `cargo test` under the hood. Each step requires the `libtest` library is built for that corresponding stage. Ideally the `test` crate would be a dev-dependency, but for now it's just easier to ensure that we sequence everything in the right order. Currently no filtering is implemented, so there's not actually a method of testing only libstd or only libcore, but rather entire swaths of crates are tested all at once. A few points of note here are: * The `coretest` and `collectionstest` crates are just listed as `[[test]]` entires for `cargo test` to naturally pick up. This mean that `cargo test -p core` actually runs all the tests for libcore. * Libraries that aren't tested all mention `test = false` in their `Cargo.toml` * Crates aren't currently allowed to have dev-dependencies due to rust-lang/cargo#860, but we can likely alleviate this restriction once workspaces are implemented. cc #31590 2016-04-29 16:23:15 -05:00
			`[[test]]`
Move libXtest into libX/tests This change moves: 1. `libcoretest` into `libcore/tests` 2. `libcollectionstest` into `libcollections/tests` This is a follow-up to #39561. 2017-04-03 09:53:04 -05:00			`name = "coretests"`
mv std libs to library/ 2020-06-11 21:31:49 -05:00			`path = "tests/lib.rs"`
rustbuild: Point to core and collections's external benchmarks. 2016-11-25 15:13:59 -06:00
Extract libcore benchmarks to a separate folder 2017-02-03 17:04:22 -06:00			`[[bench]]`
Extract collections benchmarks to libcollections/benches And libcore/benches 2017-02-06 04:38:47 -06:00			`name = "corebenches"`
mv std libs to library/ 2020-06-11 21:31:49 -05:00			`path = "benches/lib.rs"`
Ensure std benchmarks get tested. 2020-06-08 11:09:21 -05:00			`test = true`
Update Cargo submodule Required moving all fulldeps tests depending on `rand` to different locations as now there's multiple `rand` crates that can't be implicitly linked against. 2018-02-26 11:07:16 -06:00
			`[dev-dependencies]`
bump libcore tests to rand 0.7 2019-08-04 07:27:48 -05:00			`rand = "0.7"`
Add libstd and libcore Cargo features "panic_immediate_abort" It stop asserts and panics from libstd to automatically include string output and formatting code. Use case: developing static executables smaller than 50 kilobytes, where usual formatting code is excessive while keeping debuggability in debug mode. May resolve #54981. 2018-11-29 15:06:10 -06:00
			`[features]`
			`# Make panics and failed asserts immediately abort without formatting any message`
			`panic_immediate_abort = []`