Matthias Krüger d4d0c840b3 Rollup merge of #115770 - ouz-a:match_elem_builder, r=lcnr ... Match on elem first while building move paths While working on https://github.com/rust-lang/rust/pull/115025 `@lcnr` and I observed "move_paths_for" function matched on the `Ty` instead of `Projection` which seems flawed as it's the `Projection`s that cause the problem not the type. r? `@lcnr`		2023-09-22 23:12:34 +02:00
..
framework	Take &mut Results in ResultsVisitor	2023-09-02 19:35:51 -04:00
impls	when terminating during unwinding, show the reason why	2023-08-24 13:28:26 +02:00
move_paths	match array for constantindex and subslice	2023-09-22 16:28:45 +03:00
drop_flag_effects.rs	Treat Drop as a rmw operation	2023-01-30 00:20:40 +01:00
elaborate_drops.rs	rename mir::Constant -> mir::ConstOperand, mir::ConstKind -> mir::Const	2023-09-21 08:12:30 +02:00
errors.rs	Migrate all diagnostics	2022-10-23 10:09:44 +02:00
lib.rs	Rename MaybeUnreachable.	2023-08-16 18:12:18 +00:00
rustc_peek.rs	rename mir::Constant -> mir::ConstOperand, mir::ConstKind -> mir::Const	2023-09-21 08:12:30 +02:00
storage.rs	Replace Body::basic_blocks() with field access	2022-08-26 14:27:08 +02:00
un_derefer.rs	optimization round 2	2023-07-10 20:46:01 -07:00
value_analysis.rs	rename mir::Constant -> mir::ConstOperand, mir::ConstKind -> mir::Const	2023-09-21 08:12:30 +02:00