rust/compiler/rustc_pattern_analysis/src, branch 1.83.0

cleanup: don't clone types that are Copy

2024-09-29T11:31:30+00:00

remove couple redundant clones

2024-09-28T11:42:37+00:00

Rollup merge of #130715 - compiler-errors:mir-build-const-eval, r=BoxyUwU

2024-09-23T04:45:36+00:00

Replace calls to `ty::Const::{try_}eval` in mir build/pattern analysis We normalize consts in writeback: #130645. This means that consts are gonna be as normalized as they're ever gonna get in MIR building and pattern analysis. Therefore we can just use `try_to_target_usize` rather than calling `eval_target_usize`. Regarding the `.expect` calls, I'm not totally certain whether they're correct given rigid unevaluated consts. But this PR shouldn't make *more* ICEs occur; we may have to squash these ICEs when mGCE comes around, tho 😺

Reformat using the new identifier sorting from rustfmt

2024-09-22T23:11:29+00:00

Replace calls to Const::eval in mir build

2024-09-22T18:12:37+00:00

Revert warning empty patterns as unreachable

2024-09-11T16:36:45+00:00

Rollup merge of #128934 - Nadrieril:fix-empty-non-exhaustive, r=compiler-errors

2024-09-03T17:13:24+00:00

Non-exhaustive structs may be empty This is a follow-up to a discrepancy noticed in https://github.com/rust-lang/rust/pull/122792: today, the following struct is considered inhabited (non-empty) outside its defining crate: ```rust #[non_exhaustive] pub struct UninhabitedStruct { pub never: !, // other fields } ``` `#[non_exhaustive]` on a struct should mean that adding fields to it isn't a breaking change. There is no way that adding fields to this struct could make it non-empty since the `never` field must stay and is inconstructible. I suspect this was implemented this way due to confusion with `#[non_exhaustive]` enums, which indeed should be considered non-empty outside their defining crate. I propose that we consider such a struct uninhabited (empty), just like it would be without the `#[non_exhaustive]` annotation. Code that doesn't pass today and will pass after this: ```rust // In a different crate fn empty_match_on_empty_struct(x: UninhabitedStruct) -> T { match x {} } ``` This is not a breaking change. r? ``@compiler-errors``

Non-exhaustive structs may be empty

2024-09-02T19:16:37+00:00

chore: Fix typos in 'compiler' (batch 2)

2024-09-02T05:50:22+00:00

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

2024-08-29T10:18:44+00:00