rust/compiler/rustc_parse/src/parser, branch tryhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=try2025-07-17T10:06:26+00:00parse `const trait Trait`2025-07-17T10:06:26+00:00Deadbeefent3rm4n@gmail.com2025-07-13T08:49:19+00:00urn:sha1:69326878eeabb713e2d4a85215b87f18e498313cRollup merge of #143941 - folkertdev:cfg-select-docs, r=traviscross2025-07-15T10:52:44+00:00Samuel Tardieusam@rfc1149.net2025-07-15T10:52:44+00:00urn:sha1:010e3ef1137b313eb6aad8c4044b491b8b9f84dc
update `cfg_select!` documentation
tracking issue: https://github.com/rust-lang/rust/issues/115585
After rust-lang/rust#143461, and with an eye on a soon(ish) stabilization, I think the docs need some work.
The existing text read more like a motivation for the feature existing to me, so I've tried to now be a bit more descriptive. Still, suggestions are very welcome.
I also added a test for an empty `select! {}` because it's just the sort of thing that might break.
r? ``@traviscross``
Rollup merge of #143905 - xizheyin:143828, r=compiler-errors2025-07-15T10:52:40+00:00Samuel Tardieusam@rfc1149.net2025-07-15T10:52:40+00:00urn:sha1:281990eb16494ca72fe81e6ebe225d3298baae1f
Recover and suggest to use `;` to construct array type
Fixes rust-lang/rust#143828
r? compiler
Recover and suggest use `;` to construct array type2025-07-15T04:00:46+00:00xizheyinxizheyin@smail.nju.edu.cn2025-07-13T20:28:20+00:00urn:sha1:ed88af21637ff3677100fd26f8db354cd6134ad4
Signed-off-by: xizheyin <xizheyin@smail.nju.edu.cn>
update `cfg_select!` documentation2025-07-14T20:29:28+00:00Folkert de Vriesfolkert@folkertdev.nl2025-07-14T09:03:16+00:00urn:sha1:d0153f5872c484dff2a4b0ef6cad45c1f14fa1b7
and make internal terminology consistent
Co-authored-by: Travis Cross <tc@traviscross.com>
Auto merge of #143461 - folkertdev:cfg-select-builtin-macro, r=petrochenkov2025-07-13T18:34:13+00:00borsbors@rust-lang.org2025-07-13T18:34:13+00:00urn:sha1:e9182f195b8505c87c4bd055b9f6e114ccda0981
make `cfg_select` a builtin macro
tracking issue: https://github.com/rust-lang/rust/issues/115585
This parses mostly the same as the `macro cfg_select` version, except:
1. wrapping in double brackets is no longer supported (or needed): `cfg_select {{ /* ... */ }}` is now rejected.
2. in an expression context, the rhs is no longer wrapped in a block, so that this now works:
```rust
fn main() {
println!(cfg_select! {
unix => { "foo" }
_ => { "bar" }
});
}
```
3. a single wildcard rule is now supported: `cfg_select { _ => 1 }` now works
I've also added an error if none of the rules evaluate to true, and warnings for any arms that follow the `_` wildcard rule.
cc `@traviscross` if I'm missing any feature that should/should not be included
r? `@petrochenkov` for the macro logic details
make `cfg_select` a builtin macro2025-07-13T12:34:40+00:00Folkert de Vriesfolkert@folkertdev.nl2025-07-04T21:56:16+00:00urn:sha1:3689b80b75bb400e740897ec83e64be332098c0dRemove uncessary parens in closure body with unused lint2025-07-10T01:25:56+00:00yukangmoorekang@gmail.com2025-06-29T03:40:59+00:00urn:sha1:93db9e7ee01d61cb97b4f7b3d61903477910cae2Rollup merge of #143589 - RalfJung:const-pat, r=compiler-errors2025-07-08T01:09:58+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-07-08T01:09:58+00:00urn:sha1:65dded838703fddfb8f3f9b3e4741cb4e34b9f06
const-block-as-pattern: do not refer to no-longer-existing nightly feature
Surely everyone who used this nightly feature has fixed their code by now. So let's not confused people on stable that try to use a const block as a pattern by referring to some dead nightly feature.
const-block-as-pattern: do not refer to no-longer-existing nightly feature2025-07-07T14:18:41+00:00Ralf Jungpost@ralfj.de2025-07-07T14:18:35+00:00urn:sha1:1a6eff747fa5152e6fae64c8ee1167a0c587dc98