diff options
| author | bors <bors@rust-lang.org> | 2022-12-17 03:11:39 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-12-17 03:11:39 +0000 |
| commit | 74699b82cac980b9fb423a4ec2f131209b6a7630 (patch) | |
| tree | 37cd492b0fbb24d2a2842580f3261e5b630b1cdd /library/std/src/sys/unix/stdio.rs | |
| parent | 998e1a91db6a326c87c271e0fb9352d32e23ed0e (diff) | |
| parent | af7f2222d334145d37172d2c45d01277f86c6041 (diff) | |
| download | rust-74699b82cac980b9fb423a4ec2f131209b6a7630.tar.gz rust-74699b82cac980b9fb423a4ec2f131209b6a7630.zip | |
Auto merge of #105811 - ojeda:Dwarnings-no_fp_fmt_parse, r=Mark-Simulacrum
core: ensure `no_fp_fmt_parse` builds are warning-free Rust recently introduced a new `unused_imports` warning in `no_fp_fmt_parse` builds, which was fixed in https://github.com/rust-lang/rust/pull/105434. To avoid accumulating more over time, let's keep the builds warning-free. This ensures projects compiling `core` with this custom config do not see the warnings in the future and that they can keep enabling `-Dwarnings`. Similarly, https://github.com/rust-lang/rust/pull/98652 did it for `alloc`'s `no_global_oom_handling`.
Diffstat (limited to 'library/std/src/sys/unix/stdio.rs')
0 files changed, 0 insertions, 0 deletions