dnrops
/
rust
mirror of https://github.com/rust-lang/rust.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
rust/library/alloc/Cargo.toml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

56 lines
1.5 KiB
TOML
Raw Normal View History

bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies.
2016-01-22 07:19:23 +08:00
[package]
name = "alloc"
version = "0.0.0"
Add license metadata for std dependencies
2021-02-21 02:18:01 +08:00
license = "MIT OR Apache-2.0"
repository = "https://github.com/rust-lang/rust.git"
description = "The Rust core allocation and collections library"
Switch to 1.26 bootstrap compiler
2018-05-11 02:02:19 +08:00
autotests = false
autobenches = false
Switch all libraries to the 2021 edition
2021-12-17 21:53:28 +08:00
edition = "2021"
bootstrap: Add a bunch of Cargo.toml files These describe the structure of all our crate dependencies.
2016-01-22 07:19:23 +08:00
[dependencies]
mv std libs to library/
2020-06-12 10:31:49 +08:00
core = { path = "../core" }
Update compiler-builtins version to 0.1.118
2024-08-08 20:42:44 +08:00
compiler_builtins = { version = "0.1.118", features = ['rustc-dep-of-std'] }
Merge crate `collections` into `alloc`
2017-06-14 06:52:59 +08: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-02 03:32:13 +08:00
[dev-dependencies]
Update rand in the stdlib tests, and remove the getrandom feature from it
2022-11-21 08:55:41 +08:00
rand = { version = "0.8.5", default-features = false, features = ["alloc"] }
rand_xorshift = "0.3.0"
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-02 03:32:13 +08:00
Merge crate `collections` into `alloc`
2017-06-14 06:52:59 +08:00
[[test]]
Rename `{collections=>alloc}{tests,benches}`
2023-11-26 20:04:56 +08:00
name = "alloctests"
mv std libs to library/
2020-06-12 10:31:49 +08:00
path = "tests/lib.rs"
Merge crate `collections` into `alloc`
2017-06-14 06:52:59 +08:00
Move `test_shrink_to_unwind` to its own file. This way, no other test can be tripped up by `test_shrink_to_unwind` changing the alloc error hook.
2024-05-08 03:43:54 +08:00
[[test]]
name = "vec_deque_alloc_error"
path = "tests/vec_deque_alloc_error.rs"
Merge crate `collections` into `alloc`
2017-06-14 06:52:59 +08:00
[[bench]]
Rename `{collections=>alloc}{tests,benches}`
2023-11-26 20:04:56 +08:00
name = "allocbenches"
mv std libs to library/
2020-06-12 10:31:49 +08:00
path = "benches/lib.rs"
Ensure std benchmarks get tested.
2020-06-09 00:09:21 +08:00
test = true
Add benchmark for VecDeque append
2018-08-11 03:52:00 +08:00
[[bench]]
name = "vec_deque_append_bench"
mv std libs to library/
2020-06-12 10:31:49 +08:00
path = "benches/vec_deque_append.rs"
Add benchmark for VecDeque append
2018-08-11 03:52:00 +08: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-15 01:05:31 +08: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-15 05:43:43 +08:00
compiler-builtins-c = ["compiler_builtins/c"]
Update `compiler_builtins` to 0.1.39
2020-12-10 03:48:08 +08:00
compiler-builtins-no-asm = ["compiler_builtins/no-asm"]
Update compiler_builtins to 0.1.114 The `weak-intrinsics` feature was removed from compiler_builtins in https://github.com/rust-lang/compiler-builtins/pull/598, so dropped the `compiler-builtins-weak-intrinsics` feature from alloc/std/sysroot. In https://github.com/rust-lang/compiler-builtins/pull/593, some builtins for f16/f128 were added. These don't work for all compiler backends, so add a `compiler-builtins-no-f16-f128` feature and disable it for cranelift and gcc. Also disable it for LLVM targets that don't support it.
2024-05-11 21:56:59 +08:00
compiler-builtins-no-f16-f128 = ["compiler_builtins/no-f16-f128"]
add options to use optimized and mangled compiler builtins
2020-10-28 14:54:30 +08:00
compiler-builtins-mangled-names = ["compiler_builtins/mangled-names"]
Increase the reach of panic_immediate_abort
2023-10-26 07:46:06 +08:00
# Make panics and failed asserts immediately abort without formatting any message
Forward alloc features to core
2024-05-14 04:20:32 +08:00
panic_immediate_abort = ["core/panic_immediate_abort"]
Add flag to std and alloc too
2024-05-11 20:20:03 +08:00
# Choose algorithms that are optimized for binary size instead of runtime performance
Forward alloc features to core
2024-05-14 04:20:32 +08:00
optimize_for_size = ["core/optimize_for_size"]
Update check-cfg lists for alloc
2024-05-20 07:14:48 +08:00
[lints.rust.unexpected_cfgs]
level = "warn"
check-cfg = [
'cfg(bootstrap)',
addresss reviews
2024-05-20 23:06:14 +08:00
'cfg(no_global_oom_handling)',
Update check-cfg lists for alloc
2024-05-20 07:14:48 +08:00
'cfg(no_rc)',
'cfg(no_sync)',
]