rust/compiler/rustc_mir_build/src, branch masterhttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=master2025-10-02T01:54:48+00:00Auto merge of #147055 - beepster4096:subtype_is_not_a_projection, r=lcnr2025-10-02T01:54:48+00:00borsbors@rust-lang.org2025-10-02T01:54:48+00:00urn:sha1:42b384ec0dfcd528d99a4db0a337d9188a9eecaa
Turn ProjectionElem::Subtype into CastKind::Subtype
I noticed that drop elaboration can't, in general, handle `ProjectionElem::SubType`. It creates a disjoint move path that overlaps with other move paths. (`Subslice` does too, and I'm working on a different PR to make that special case less fragile.) If its skipped and treated as the same move path as its parent then `MovePath.place` has multiple possible projections. (It would probably make sense to remove all `Subtype` projections for the canonical place but it doesn't make sense to have this special case for a problem that doesn't actually occur in real MIR.)
The only reason this doesn't break is that `Subtype` is always the sole projection of the local its applied to. For the same reason, it works fine as a `CastKind` so I figured that makes more sense than documenting and validating this hidden invariant.
cc rust-lang/rust#112651, rust-lang/rust#133258
r? Icnr (bc you've been the main person dealing with `Subtype` it looks like)
Rollup merge of #141469 - Kivooeo:remove-usnsafegate, r=compiler-errors2025-09-28T16:13:11+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-09-28T16:13:11+00:00urn:sha1:6059195875986ac9d928d1059d733d518cb1709b
Allow `&raw [mut | const]` for union field in safe code
fixes rust-lang/rust#141264
r? ``@Veykril``
Unresolved questions:
- [x] Any edge cases?
- [x] How this works with rust-analyzer (because all I've did is prevent compiler from emitting error in `&raw` context) (rust-lang/rust-analyzer#19867)
- [x] Should we allow `addr_of!` and `addr_of_mut!` as well? In current version they both (`&raw` and `addr_of!`) are allowed (They are the same)
- [x] Is chain of union fields is a safe? (Yes)
Rollup merge of #146745 - helldawg:master, r=workingjubilee2025-09-28T07:15:23+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-09-28T07:15:23+00:00urn:sha1:4eddf645bf4d19fe52d1cf607ae3dc0e13787809
Clarified error note for usize range matching
Fixes rust-lang/rust#146476
This is kinda rough, but it gets the point across a little better and stays short.
fix doc comments to be more standard2025-09-26T09:25:56+00:00Marijn Schoutenmhkbst@gmail.com2025-09-25T09:30:31+00:00urn:sha1:fc703ec5c88e678a4931f7bb8ed86efc141775f7ProjectionElem::Subtype -> CastKind::Subtype2025-09-26T08:25:26+00:00beepster409619316085+beepster4096@users.noreply.github.com2025-09-26T03:54:54+00:00urn:sha1:aa5a21450a070fdea66a07d3cab3b69e6735c328usize/isize range matching error clarification2025-09-25T15:15:04+00:00helldawg116204326+helldawg@users.noreply.github.com2025-09-19T01:59:14+00:00urn:sha1:7e58c9110521d960cb97e730dfe700b3ec64c9abmark THIR use as candidate for constness check2025-09-24T17:54:25+00:00Ding Xiang Feidingxiangfei2009@protonmail.ch2025-09-24T17:53:34+00:00urn:sha1:b77de834c031890c048f8164d4b5979d2511c00edo not materialise X in [X; 0] when X is unsizing a const2025-09-24T17:54:23+00:00Ding Xiang Feidingxiangfei2009@protonmail.ch2025-08-11T22:39:50+00:00urn:sha1:a86f14072714fb817a6f60fa20be5a4e875d049fRemove Rvalue::Len.2025-09-16T22:23:19+00:00Camille Gillotgillot.camille@gmail.com2025-09-14T22:29:04+00:00urn:sha1:53b91ea87fe4b430c33bd22dfdaaa6289bf9466aDriveby fixes2025-09-09T12:49:16+00:00Boxyrust@boxyuwu.dev2025-08-22T11:31:34+00:00urn:sha1:332d8d62356a1be77bfe6412ab5ed3fa33ae9af6