rust/compiler/rustc_const_eval/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)
remove explicit deref of AbiAlign for most methods2025-09-28T22:02:14+00:00Jubilee Youngworkingjubilee@gmail.com2025-09-28T21:40:39+00:00urn:sha1:0c9d0dfe046f0674f0507df564504ac3bac862d9
Much of the compiler calls functions on Align projected from AbiAlign.
AbiAlign impls Deref to its inner Align, so we can simplify these away.
Also, it will minimize disruption when AbiAlign is removed.
For now, preserve usages that might resolve to PartialOrd or PartialEq,
as those have odd inference.
Apply cfg(bootstrap) replacement2025-09-26T23:09:23+00:00Mark Rousskovmark.simulacrum@gmail.com2025-09-16T02:01:36+00:00urn:sha1:201f299ef6039886042ad8dd7c76a4fbd1a77a3fProjectionElem::Subtype -> CastKind::Subtype2025-09-26T08:25:26+00:00beepster409619316085+beepster4096@users.noreply.github.com2025-09-26T03:54:54+00:00urn:sha1:aa5a21450a070fdea66a07d3cab3b69e6735c328Rollup merge of #146991 - cachebag:span-caller-location, r=RalfJung2025-09-26T04:36:32+00:00Matthias Krüger476013+matthiaskrgr@users.noreply.github.com2025-09-26T04:36:32+00:00urn:sha1:b184550f0ede53826ac03aeb107c46e43e39d232
const_caller_location to use real Span instead of `DUMMY_SP`
Clarifying usage of DUMMY_SP
const_caller_location: edit FIXME to explain use of `DUMMY_SP`2025-09-25T20:09:27+00:00Akrm Al-Hakimialhakimiakrmj@gmail.com2025-09-25T17:57:59+00:00urn:sha1:c98b3b2da46146956b982e4ae1747c3614a461fd
Co-authored-by: Ralf Jung <post@ralfj.de>
Rollup merge of #146735 - Qelxiros:const_mul_add, r=tgross35,RalfJung2025-09-25T10:31:54+00:00Stuart CookZalathar@users.noreply.github.com2025-09-25T10:31:54+00:00urn:sha1:8e62f95376e40f3eb81e5f1b29cb4eb997c36fb5
unstably constify float mul_add methods
Tracking issue: rust-lang/rust#146724
r? `@tgross35`
unstably constify float mul_add methods2025-09-24T19:21:31+00:00Jeremy Smartjeremy3141592@gmail.com2025-09-18T19:02:49+00:00urn:sha1:a00f24116e9bcecc8c73f9f7ec0c399964b37a92
Co-authored-by: Ralf Jung <post@ralfj.de>
const validation: better error for maybe-null references2025-09-24T11:35:29+00:00Ralf Jungpost@ralfj.de2025-09-24T10:12:41+00:00urn:sha1:8328c3dada0c888b1c570f97314b3f697d4b2a96const-eval: improve and actually test the errors when pointers might be outside the range of a scalar2025-09-24T11:34:33+00:00Ralf Jungpost@ralfj.de2025-09-22T17:46:30+00:00urn:sha1:0a41add6293d76b165968d70f95e7edbbe65fe11