rust/compiler/rustc_mir/src
Nicholas-Baron 261ca04c92 Changed unwrap_or to unwrap_or_else in some places.
The discussion seems to have resolved that this lint is a bit "noisy" in
that applying it in all places would result in a reduction in
readability.

A few of the trivial functions (like `Path::new`) are fine to leave
outside of closures.

The general rule seems to be that anything that is obviously an
allocation (`Box`, `Vec`, `vec![]`) should be in a closure, even if it
is a 0-sized allocation.
2020-11-10 20:07:47 -08:00
..
borrow_check Changed unwrap_or to unwrap_or_else in some places. 2020-11-10 20:07:47 -08:00
const_eval Rollup merge of #78742 - vn-ki:fix-issue-78655, r=oli-obk 2020-11-05 10:29:59 +01:00
dataflow Add comments to explain memory usage optimization 2020-11-09 13:34:16 -08:00
interpret inliner: Use substs_for_mir_body 2020-11-06 00:00:00 +00:00
monomorphize Rollup merge of #78875 - petrochenkov:cleantarg, r=Mark-Simulacrum 2020-11-10 14:45:21 +01:00
transform Rollup merge of #78847 - tmiasko:inline-return-place, r=matthewjasper 2020-11-10 14:45:17 +01:00
util use single char patterns for split() (clippy::single_char_pattern) 2020-11-07 07:27:44 +01:00
lib.rs TypeVisitor: use ControlFlow in rustc_{mir,privacy,traits,typeck} 2020-10-30 12:27:44 +01:00
shim.rs rustc_mir: support MIR-inlining #[track_caller] functions. 2020-10-21 04:43:56 +03:00