6 commits

Author	SHA1	Message	Date
Camille GILLOT	547af00019	Remove on_all_drop_children_bits. ... As drop elaboration only tracks places that need dropping, is has become equivalent to `on_all_children_bits`.	2023-10-21 10:33:37 +00:00
Camille GILLOT	a8e56d0b0b	Remove is_terminal_path. ... That information is redundant. Is the path is terminal, `first_child` will already be `None`.	2023-10-21 10:26:28 +00:00
Giacomo Pasini	68c1e2fd48	Treat Drop as a rmw operation ... Previously, a Drop terminator was considered a move in MIR. This commit changes the behavior to only treat Drop as a mutable access to the dropped place. In order for this change to be correct, we need to guarantee that a) A dropped value won't be used again b) Places that appear in a drop won't be used again before a subsequent initialization. We can ensure this to be correct at MIR construction because Drop will only be emitted when a variable goes out of scope, thus having: (a) as there is no way of reaching the old value. drop-elaboration will also remove any uninitialized drop. (b) as the place can't be named following the end of the scope. However, the initialization status, previously tracked by moves, should also be tied to the execution of a Drop, hence the additional logic in the dataflow analyses.	2023-01-30 00:20:40 +01:00
Nicholas Nethercote	68a19209e0	Inline and remove place_contents_drop_state_cannot_differ. ... It has a single call site and is hot enough to be worth inlining. And make sure `is_terminal_path` is inlined, too.	2022-12-08 13:59:29 +11:00
est31	2ef8af6619	Adopt let else in more places	2022-02-19 17:27:43 +01:00
Camille GILLOT	fd9c04fe32	Move the dataflow framework to its own crate.	2021-09-07 19:57:07 +02:00

Renamed from compiler/rustc_mir/src/dataflow/drop_flag_effects.rs (Browse further)