https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=stable 2025-05-06T08:49:25+00:00 2025-05-06T08:49:25+00:00 Jieyou Xu jieyouxu@outlook.com 2025-05-05T18:37:45+00:00 urn:sha1:cbaa73beca9a7b62c6400669e47e09958e8804ab And also: - Document test intent. - Move under `link-native-libs/` instead. 2025-04-17T11:21:54+00:00 bors bors@rust-lang.org 2025-04-17T11:21:54+00:00 urn:sha1:883f9f72e87ccb6838d528d8158ea6323baacc65 Rollup of 8 pull requests Successful merges: - #138632 (Stabilize `cfg_boolean_literals`) - #139416 (unstable book; document `macro_metavar_expr_concat`) - #139782 (Consistent with treating Ctor Call as Struct in liveness analysis) - #139885 (document RUSTC_BOOTSTRAP, RUSTC_OVERRIDE_VERSION_STRING, and -Z allow-features in the unstable book) - #139904 (Explicitly annotate edition for `unpretty=expanded` and `unpretty=hir` tests) - #139932 (transmutability: Refactor tests for simplicity) - #139944 (Move eager translation to a method on Diag) - #139948 (git: ignore `60600a6fa403216bfd66e04f948b1822f6450af7` for blame purposes) r? `@ghost` `@rustbot` modify labels: rollup 2025-04-17T04:25:15+00:00 Matthias Krüger 476013+matthiaskrgr@users.noreply.github.com 2025-04-17T04:25:15+00:00 urn:sha1:0de803c38d33655ed3ec25e237b6c1e2bb4e7426 Stabilize `cfg_boolean_literals` Closes #131204 `@rustbot` labels +T-lang +I-lang-nominated This will end up conflicting with the test in #138293 so whichever doesn't land first will need updating -- # Stabilization Report ## General design ### What is the RFC for this feature and what changes have occurred to the user-facing design since the RFC was finalized? [RFC 3695](https://github.com/rust-lang/rfcs/pull/3695), none. ### What behavior are we committing to that has been controversial? Summarize the major arguments pro/con. None ### Are there extensions to this feature that remain unstable? How do we know that we are not accidentally committing to those? None ## Has a call-for-testing period been conducted? If so, what feedback was received? Yes; only positive feedback was received. ## Implementation quality ### Summarize the major parts of the implementation and provide links into the code (or to PRs) Implemented in [#131034](https://github.com/rust-lang/rust/pull/131034). ### Summarize existing test coverage of this feature - [Basic usage, including `#[cfg()]`, `cfg!()` and `#[cfg_attr()]`](https://github.com/rust-lang/rust/blob/6d71251cf9e40326461f90f8ff9a7024706aea87/tests/ui/cfg/true-false.rs) - [`--cfg=true/false` on the command line being accessible via `r#true/r#false`](https://github.com/rust-lang/rust/blob/6d71251cf9e40326461f90f8ff9a7024706aea87/tests/ui/cfg/raw-true-false.rs) - [Interaction with the unstable `#[doc(cfg(..))]` feature](https://github.com/rust-lang/rust/tree/6d71251/tests/rustdoc-ui/cfg-boolean-literal.rs) - [Denying `--check-cfg=cfg(true/false)`](https://github.com/rust-lang/rust/tree/6d71251/tests/ui/check-cfg/invalid-arguments.rs) - Ensuring `--cfg false` on the command line doesn't change the meaning of `cfg(false)`: `tests/ui/cfg/cmdline-false.rs` - Ensuring both `cfg(true)` and `cfg(false)` on the same item result in it being disabled: `tests/ui/cfg/both-true-false.rs` ### What outstanding bugs in the issue tracker involve this feature? Are they stabilization-blocking? The above mentioned issue; it should not block as it interacts with another unstable feature. ### What FIXMEs are still in the code for that feature and why is it ok to leave them there? None ### Summarize contributors to the feature by name for recognition and assuredness that people involved in the feature agree with stabilization - `@clubby789` (RFC) - `@Urgau` (Implementation in rustc) ### Which tools need to be adjusted to support this feature. Has this work been done? `rustdoc`'s unstable`#[doc(cfg(..)]` has been updated to respect it. `cargo` has been updated with a forward compatibility lint to enable supporting it in cargo once stabilized. ## Type system and execution rules ### What updates are needed to the reference/specification? (link to PRs when they exist) A few lines to be added to the reference for configuration predicates, specified in the RFC. 2025-04-16T19:44:02+00:00 Obei Sideg obei.sideg@gmail.com 2025-04-08T02:31:24+00:00 urn:sha1:d17c04e4a220d6f7bf170eeb0f90498e215555fa 2025-04-13T18:48:53+00:00 Vadim Petrochenkov vadim.petrochenkov@gmail.com 2025-04-12T19:40:34+00:00 urn:sha1:93bee0789a45ea7d5d65bb9301c4ad5ece3abeb2 when possible. 2025-04-03T21:41:58+00:00 clubby789 jamie@hill-daniel.co.uk 2025-03-29T17:24:03+00:00 urn:sha1:303c1b45c29f8bb186a9a95cb56643d1aef773fa 2025-04-03T08:08:55+00:00 Vadim Petrochenkov vadim.petrochenkov@gmail.com 2025-03-28T23:41:32+00:00 urn:sha1:4d649906900cd833b0680f53b8c197b087711a4a 2025-03-25T14:33:09+00:00 Vadim Petrochenkov vadim.petrochenkov@gmail.com 2025-03-23T12:50:51+00:00 urn:sha1:8d5109aa6ea1b54a560774eb95ba7c1b8d404faa 2025-02-12T03:42:47+00:00 Jubilee Young workingjubilee@gmail.com 2025-02-12T03:40:29+00:00 urn:sha1:32fd1a7b7205d1f8ccf168c22dada83ea38e3adb Most of these just format the ABI string, so... just format ExternAbi? This makes it more consistent and less jank when we can do it. 2025-01-07T15:04:14+00:00 Mara Bos m-ou.se@m-ou.se 2024-10-31T10:39:45+00:00 urn:sha1:585c9765a203df7cc7b497d848aae4ba979fcb39