rust/rustc_mir at d4ea0b3e46a0303d5802b632e88ba1ba84d9d16f - rust

History

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
..
src	Changed unwrap_or to unwrap_or_else in some places.	2020-11-10 20:07:47 -08:00
Cargo.toml	Use `tracing` spans to trace the entire MIR interp stack	2020-09-28 20:07:57 +02:00

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

src Changed unwrap_or to unwrap_or_else in some places. 2020-11-10 20:07:47 -08:00

Cargo.toml Use tracing spans to trace the entire MIR interp stack 2020-09-28 20:07:57 +02:00