rust/compiler/rustc_const_eval/src/interpret, branch master

Auto merge of #147055 - beepster4096:subtype_is_not_a_projection, r=lcnr

2025-10-02T01:54:48+00:00

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 methods

2025-09-28T22:02:14+00:00

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.

ProjectionElem::Subtype -> CastKind::Subtype

2025-09-26T08:25:26+00:00

Rollup merge of #146735 - Qelxiros:const_mul_add, r=tgross35,RalfJung

2025-09-25T10:31:54+00:00

unstably constify float mul_add methods Tracking issue: rust-lang/rust#146724 r? `@tgross35`

unstably constify float mul_add methods

2025-09-24T19:21:31+00:00

Co-authored-by: Ralf Jung

const validation: better error for maybe-null references

2025-09-24T11:35:29+00:00

const-eval: improve and actually test the errors when pointers might be outside the range of a scalar

2025-09-24T11:34:33+00:00

Rollup merge of #146664 - fmease:clean-up-dyn, r=jdonszelmann

2025-09-18T01:48:51+00:00

Clean up `ty::Dynamic` 1. As a follow-up to PR rust-lang/rust#143036, remove `DynKind` entirely. 2. Inside HIR ty lowering, consolidate modules `dyn_compatibility` and `lint` into `dyn_trait` * `dyn_compatibility` wasn't about dyn compatibility itself, it's about lowering trait object types * `lint` contained dyn-Trait-specific diagnostics+lints only

Auto merge of #146331 - RalfJung:copy-prov-repeat, r=oli-obk

2025-09-17T13:56:54+00:00

interpret: copy_provenance: avoid large intermediate buffer for large repeat counts Copying provenance worked in this odd way where the "preparation" phase (which is supposed to just extract the necessary information from the source range) already did all the work of repeating the result N times for the target range. This was needed to use the existing `insert_presorted` function on `SortedMap`. This PR generalizes `insert_presorted` so that we can avoid this odd structure on copy-provenance, and maybe even improve performance.

Remove `DynKind`

2025-09-17T02:46:46+00:00