rust/compiler/rustc_pattern_analysis/tests, branch masterhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=master2025-07-27T23:01:39+00:00In rustc_pattern_analysis, put `true` witnesses before `false` witnesses2025-07-27T23:01:39+00:00Chayim Refael Friedmanchayimfr@gmail.com2025-07-27T21:01:28+00:00urn:sha1:6bf3cbe39e09f4d9187a0b1f6a7bd45101f7aad8
In rustc it doesn't really matter what the order of the witnesses is, but I'm planning to use the witnesses for implementing the "add missing match arms" assist in rust-analyzer, and there `true` before `false` is the natural order (like `Some` before `None`), and also what the current assist does.
The current order doesn't seem to be intentional; the code was created when bool ctors became their own thing, not just int ctors, but for integer, 0 before 1 is indeed the natural order.
Silence a warning2025-07-20T16:27:30+00:00Nadrierilnadrieril+git@gmail.com2025-07-19T20:14:12+00:00urn:sha1:af07c08c60fe779c2e73c561403cb5edf4f15e9bList all the variants of non-exhaustive enums in exhaustive mode2025-07-20T16:27:30+00:00Nadrierilnadrieril+git@gmail.com2025-07-19T19:18:14+00:00urn:sha1:9b01de20e10376d379ae32baa6a315d8e30cb351pattern_analysis: add option to get a full set of witnesses2025-07-20T16:27:30+00:00Nadrierilnadrieril+git@gmail.com2025-07-19T09:28:31+00:00urn:sha1:2bb00741d463143a10e632bb118d4ed336dbb75falways check for mixed deref pattern and normal constructors2025-07-05T06:47:31+00:00diannediannes.gm@gmail.com2025-07-05T04:17:40+00:00urn:sha1:50061f3b11f51d7a6e3acd8ce793a1f17f99b597
This makes it work for box patterns and in rust-analyzer.
Use `-Wunused_crate_dependencies` for compiler crates.2025-03-19T21:59:43+00:00Nicholas Nethercoten.nethercote@gmail.com2025-03-03T07:59:30+00:00urn:sha1:8121958fda43759fa94e3f74f7cdbb595ddcc0e5
It's very useful. There are some false positives involving integration
tests in `rustc_pattern_analysis` and `rustc_serialize`. There is also a
false positive involving `rustc_driver_impl`'s
`rustc_randomized_layouts` feature. And I removed a `rustc_span` mention
in a doc comment in `rustc_log` because it wasn't integral to the
comment but caused a dev-dependency.
Add `unreachable_pub` to `RUSTC_LINT_FLAGS` for `compiler/` crates.2025-03-11T02:14:21+00:00Nicholas Nethercoten.nethercote@gmail.com2025-03-11T00:51:07+00:00urn:sha1:55505ab1d3da2ad201303674cb6d3ebeb53e395d
And fix the new errors in the handful of crates that didn't have a
`#![warn(unreachable_pub)]`.
Revert "Use workspace lints for crates in `compiler/` #138084"2025-03-10T10:12:47+00:00许杰友 Jieyou Xu (Joe)39484203+jieyouxu@users.noreply.github.com2025-03-10T10:12:34+00:00urn:sha1:063ef18fdc10cb0eb49e1af855e1a8e807e73eed
Revert <https://github.com/rust-lang/rust/pull/138084> to buy time to
consider options that avoids breaking downstream usages of cargo on
distributed `rustc-src` artifacts, where such cargo invocations fail due
to inability to inherit `lints` from workspace root manifest's
`workspace.lints` (this is only valid for the source rust-lang/rust
workspace, but not really the distributed `rustc-src` artifacts).
This breakage was reported in
<https://github.com/rust-lang/rust/issues/138304>.
This reverts commit 48caf81484b50dca5a5cebb614899a3df81ca898, reversing
changes made to c6662879b27f5161e95f39395e3c9513a7b97028.
Add `unreachable_pub` to the default lints for `compiler/` crates.2025-03-07T21:41:43+00:00Nicholas Nethercoten.nethercote@gmail.com2025-03-06T03:25:44+00:00urn:sha1:9212e31c92aba29fac1c1e05a258abe36dd0afee
And fix the new errors in the handful of crates that didn't have a
`#![warn(unreachable_pub)]`.
Greatly simplify lifetime captures in edition 20242025-02-22T22:24:52+00:00Michael Gouletmichael@errs.io2025-02-20T18:58:46+00:00urn:sha1:12e3911d81034864314503b9c2d9fba2773c7904