rust/compiler/rustc_parse/src/errors.rs, branch 1.82.0

Add `warn(unreachable_pub)` to `rustc_parser`.

2024-08-29T10:13:06+00:00

Use bool in favor of Option<()> for diagnostics

2024-08-21T05:31:11+00:00

Rollup merge of #128496 - clubby789:box-syntax-multipart, r=compiler-errors

2024-08-01T16:43:41+00:00

Fix removed `box_syntax` diagnostic if source isn't available Fix #128442

Fix removed `box_syntax` diagnostic if source isn't available

2024-08-01T13:11:24+00:00

Auto merge of #127543 - carbotaniuman:more_unsafe_attr_verification, r=estebank,traviscross

2024-08-01T10:40:45+00:00

More unsafe attr verification This code denies unsafe on attributes such as `#[test]` and `#[ignore]`, while also changing the `MetaItem` parsing so `unsafe` in args like `#[allow(unsafe(dead_code))]` is not accidentally allowed. Tracking: - https://github.com/rust-lang/rust/issues/123757

Add toggle for `parse_meta_item` unsafe parsing

2024-07-30T23:28:43+00:00

This makes it possible for the `unsafe(...)` syntax to only be valid at the top level, and the `NestedMetaItem`s will automatically reject `unsafe(...)`.

Auto merge of #128083 - Mark-Simulacrum:bump-bootstrap, r=albertlarsan68

2024-07-30T17:49:08+00:00

Bump bootstrap compiler to new beta https://forge.rust-lang.org/release/process.html#master-bootstrap-update-t-2-day-tuesday

Reformat `use` declarations.

2024-07-28T22:26:52+00:00

The previous commit updated `rustfmt.toml` appropriately. This commit is the outcome of running `x fmt --all` with the new formatting options.

step cfg(bootstrap)

2024-07-28T18:46:29+00:00

Rollup merge of #127054 - compiler-errors:bound-ordering, r=fmease

2024-07-25T02:43:18+00:00

Reorder trait bound modifiers *after* `for<...>` binder in trait bounds This PR suggests changing the grammar of trait bounds from: ``` [CONSTNESS] [ASYNCNESS] [?] [BINDER] [TRAIT_PATH] const async ? for<'a> Sized ``` to ``` ([BINDER] [CONSTNESS] [ASYNCNESS] | [?]) [TRAIT_PATH] ``` i.e., either ``` ? Sized ``` or ``` for<'a> const async Sized ``` (but not both) ### Why? I think it's strange that the binder applies "more tightly" than the `?` trait polarity. This becomes even weirder when considering that we (or at least, I) want to have `async` trait bounds expressed like: ``` where T: for<'a> async Fn(&'a ()) -> i32, ``` and not: ``` where T: async for<'a> Fn(&'a ()) -> i32, ``` ### Fallout No crates on crater use this syntax, presumably because it's literally useless. This will require modifying the reference grammar, though. ### Alternatives If this is not desirable, then we can alternatively keep parsing `for<'a>` after the `?` but deprecate it with either an FCW (or an immediate hard error), and begin parsing `for<'a>` *before* the `?`.