This option was used to gate `f16` and `f128` when support across
backends and targets was inconsistent. We now have the rustc builtin cfg
`target_has_reliable{f16,f128}` which has taken over this usecase.
Remove no-f16-f128 since it is now unused and redundant.
33 lines
859 B
TOML
33 lines
859 B
TOML
cargo-features = ["public-dependency"]
|
|
|
|
[package]
|
|
name = "alloc"
|
|
version = "0.0.0"
|
|
license = "MIT OR Apache-2.0"
|
|
repository = "https://github.com/rust-lang/rust.git"
|
|
description = "The Rust core allocation and collections library"
|
|
autotests = false
|
|
autobenches = false
|
|
edition = "2024"
|
|
|
|
[lib]
|
|
test = false
|
|
bench = false
|
|
|
|
[dependencies]
|
|
core = { path = "../core", public = true }
|
|
compiler_builtins = { path = "../compiler-builtins/compiler-builtins", features = ["rustc-dep-of-std"] }
|
|
|
|
[features]
|
|
compiler-builtins-mem = ['compiler_builtins/mem']
|
|
compiler-builtins-c = ["compiler_builtins/c"]
|
|
# Choose algorithms that are optimized for binary size instead of runtime performance
|
|
optimize_for_size = ["core/optimize_for_size"]
|
|
|
|
[lints.rust.unexpected_cfgs]
|
|
level = "warn"
|
|
check-cfg = [
|
|
'cfg(no_global_oom_handling)',
|
|
'cfg(no_rc)',
|
|
'cfg(no_sync)',
|
|
]
|