rust/rustc_middle at f77f4d55bdf9d8955d3292f709bd9830c2fdeca5 - rust

History

bors f77f4d55bd Auto merge of #107542 - compiler-errors:param-envs-with-inference-vars-are-cursed, r=jackh726 Don't call `with_reveal_all_normalized` in const-eval when `param_env` has inference vars in it what: This slightly shifts the order of operations from an existing hack: `5b6ed253c4/compiler/rustc_middle/src/ty/consts/kind.rs (L225-L230)` in order to avoid calling a tcx query (`TyCtxt::reveal_opaque_types_in_bounds`, via `ParamEnv::with_reveal_all_normalized`) when a param-env has inference variables in it. why: This allows us to enable fingerprinting of query keys/values outside of incr-comp in deubg mode, to make sure we catch other places where we're passing infer vars and other bad things into query keys. Currently that (`bbf33836b9`) crashes because we introduce inference vars into a param-env in the blanket-impl finder in rustdoc 😓 `5b6ed253c4/src/librustdoc/clean/blanket_impl.rs (L43)` See the CI failure here: https://github.com/rust-lang/rust/actions/runs/4058194838/jobs/6984834619		2023-02-18 23:43:42 +00:00
..
src	Auto merge of #107542 - compiler-errors:param-envs-with-inference-vars-are-cursed, r=jackh726	2023-02-18 23:43:42 +00:00
Cargo.toml	Give a more helpful error for "trimmed_def_paths construted"	2022-12-22 13:12:15 -06:00
README.md

For more information about how rustc works, see the rustc dev guide.