Amanda Stjerna 7b5b7a7010 Remove confusing use_polonius flag and do less cloning ... The `use_polonius` flag is both redundant and confusing since every function it's propagated to also checks if `all_facts` is `Some`, the true test of whether to generate Polonius facts for Polonius or for external consumers. This PR makes that path clearer by simply doing away with the argument and handling the logic in precisely two places: where facts are populated (check for `Some`), and where `all_facts` are initialised. It also delays some statements until after that check to avoid the miniscule performance penalty of executing them when Polonius is disabled. This also addresses @lqd's concern in #125652 by reducing the size of what is cloned out of Polonius facts to just the facts being added, as opposed to the entire vector of potential inputs, and added descriptive comments. *Reviewer note*: the comments in [add_extra_drop_facts](85f90a4612/compiler/rustc_borrowck/src/type_check/liveness/trace.rs (L219)) should be inspected by a reviewer, in particular the one on L#259 in this PR, which should be trivial for someone with the right background knowledge. I also included some minor lints I found on the way there that I couldn't help myself from addressing.		2024-06-05 10:57:27 +02:00
..
src	Remove confusing use_polonius flag and do less cloning	2024-06-05 10:57:27 +02:00
Cargo.toml	bump itertools to 0.12	2024-03-08 12:34:05 +03:00
messages.ftl	Better account for FnOnce in move errors	2024-04-11 16:41:42 +00:00