rust/library/alloc/Cargo.toml

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

[dependencies]
core = { path = "../core" }
compiler_builtins = { version = "0.1.39", features = ['rustc-dep-of-std'] }

[dev-dependencies]
rand = "0.7"
rand_xorshift = "0.2"

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

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

[[bench]]
name = "vec_deque_append_bench"
path = "benches/vec_deque_append.rs"
harness = false

[features]
compiler-builtins-mem = ['compiler_builtins/mem']
compiler-builtins-c = ["compiler_builtins/c"]
compiler-builtins-no-asm = ["compiler_builtins/no-asm"]
compiler-builtins-mangled-names = ["compiler_builtins/mangled-names"]
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 = "alloc"`
			`version = "0.0.0"`
Switch to 1.26 bootstrap compiler 2018-05-10 13:02:19 -05:00			`autotests = false`
			`autobenches = false`
liballoc => edition = 2018. 2019-02-02 01:36:03 -06: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
			`[dependencies]`
mv std libs to library/ 2020-06-11 21:31:49 -05:00			`core = { path = "../core" }`
Update `compiler_builtins` to 0.1.39 2020-12-09 13:48:08 -06:00			`compiler_builtins = { version = "0.1.39", features = ['rustc-dep-of-std'] }`
Merge crate `collections` into `alloc` 2017-06-13 17:52:59 -05:00
std: Remove `rand` crate and module This commit removes the `rand` crate from the standard library facade as well as the `__rand` module in the standard library. Neither of these were used in any meaningful way in the standard library itself. The only need for randomness in libstd is to initialize the thread-local keys of a `HashMap`, and that unconditionally used `OsRng` defined in the standard library anyway. The cruft of the `rand` crate and the extra `rand` support in the standard library makes libstd slightly more difficult to port to new platforms, namely WebAssembly which doesn't have any randomness at all (without interfacing with JS). The purpose of this commit is to clarify and streamline randomness in libstd, focusing on how it's only required in one location, hashmap seeds. Note that the `rand` crate out of tree has almost always been a drop-in replacement for the `rand` crate in-tree, so any usage (accidental or purposeful) of the crate in-tree should switch to the `rand` crate on crates.io. This then also has the further benefit of avoiding duplication (mostly) between the two crates! 2017-11-01 14:32:13 -05:00			`[dev-dependencies]`
bump rand to fix Miri failures 2019-04-19 02:37:33 -05:00			`rand = "0.7"`
			`rand_xorshift = "0.2"`
std: Remove `rand` crate and module This commit removes the `rand` crate from the standard library facade as well as the `__rand` module in the standard library. Neither of these were used in any meaningful way in the standard library itself. The only need for randomness in libstd is to initialize the thread-local keys of a `HashMap`, and that unconditionally used `OsRng` defined in the standard library anyway. The cruft of the `rand` crate and the extra `rand` support in the standard library makes libstd slightly more difficult to port to new platforms, namely WebAssembly which doesn't have any randomness at all (without interfacing with JS). The purpose of this commit is to clarify and streamline randomness in libstd, focusing on how it's only required in one location, hashmap seeds. Note that the `rand` crate out of tree has almost always been a drop-in replacement for the `rand` crate in-tree, so any usage (accidental or purposeful) of the crate in-tree should switch to the `rand` crate on crates.io. This then also has the further benefit of avoiding duplication (mostly) between the two crates! 2017-11-01 14:32:13 -05:00
Merge crate `collections` into `alloc` 2017-06-13 17:52:59 -05:00			`[[test]]`
			`name = "collectionstests"`
mv std libs to library/ 2020-06-11 21:31:49 -05:00			`path = "tests/lib.rs"`
Merge crate `collections` into `alloc` 2017-06-13 17:52:59 -05:00
			`[[bench]]`
			`name = "collectionsbenches"`
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`
Add benchmark for VecDeque append 2018-08-10 14:52:00 -05:00
			`[[bench]]`
			`name = "vec_deque_append_bench"`
mv std libs to library/ 2020-06-11 21:31:49 -05:00			`path = "benches/vec_deque_append.rs"`
Add benchmark for VecDeque append 2018-08-10 14:52:00 -05:00			`harness = false`
std: Activate compiler_builtins `mem` feature for no_std targets This was an accidental regression from #56092, but for `no_std` targets being built and distributed we want to be sure to activate the compiler-builtins `mem` feature which demangles important memory-related intrinsics. 2018-12-14 11:05:31 -06:00
			`[features]`
			`compiler-builtins-mem = ['compiler_builtins/mem']`
Update the compiler_builtins crate This updates to 0.1.13 for `compiler_builtins`, published to fix a few issues. The feature changes here are updated because `compiler_builtins` no longer enables the `c` feature by default but we want to do so through our build still. Closes #60747 Closes #60782 2019-05-14 16:43:43 -05:00			`compiler-builtins-c = ["compiler_builtins/c"]`
Update `compiler_builtins` to 0.1.39 2020-12-09 13:48:08 -06:00			`compiler-builtins-no-asm = ["compiler_builtins/no-asm"]`
add options to use optimized and mangled compiler builtins 2020-10-28 01:54:30 -05:00			`compiler-builtins-mangled-names = ["compiler_builtins/mangled-names"]`