| Age | Commit message (Collapse) | Author | Lines |
|
It's subsumed by `feature(use_extern_macros)` and `pub use`
|
|
This is in the matter of RFC 1940 and tracking issue #43302.
|
|
Fixes #49632
|
|
The unstable-feature attribute requires an issue (neglecting it is
E0547), which gets used in the error messages. Unfortunately, there are
some cases where "0" is apparently used a placeholder where no issue
exists, directing the user to see the (nonexistent) issue #0. (It would
have been better to either let `issue` be optional—compare to how issue
is an `Option<u32>` in the feature-gate declarations in
libsyntax/feature-gate.rs—or actually require that an issue be created.)
Rather than endeavoring to change how `#[unstable]` works at this time
(given competing contributor and reviewer priorities), this simple patch
proposes the less-ambitious solution of just not adding the "(see
issue)" note when the number is zero.
Resolves #49983.
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #44798 and rust-lang/cargo#4948.
|
|
|
|
|
|
|
|
|
|
|
|
This'll enable running queries that could be cached and overall be more amenable
to the query infastructure.
|
|
The `#[simd]` attribute has been deprecated since c8b6d5b23cc8b2d43ece9f06252c7e98280fb8e5 back in 2015. Any nightly crates using it have had ample time to switch to `#[repr(simd)]`, and if they didn't they're likely broken by now anyway.
|
|
This ensures that if we emit the same diagnostic twice, the error count will
match the real number of errors shown to the user.
Fixes #42106
|
|
|
|
Renames only in this commit, and obviously
.stderr file additions.
|