Matthias Krüger 548d49c789 Rollup merge of #105847 - compiler-errors:issue-104396, r=oli-obk ... Ensure param-env is const before calling `eval_to_valtree` Other queries call `ParamEnv::with_const` *inside* of the query itself (e.g. `const_eval_global_id_for_typeck`), so this could alternatively be moved into the provider of `eval_to_valtree` instead. I don't have a particularly strong opinion, though *theoretically* caching is better if we make the query keys more constrained. I'm not exactly sure how this is an effect of the `-Zmir-opt-level=3` flag. Maybe something about the inliner causes us to inline an unevaluated const into a body where it can be evaluated, but where it has not yet been normalized. This seems likely, since we're inlining `from_fn_1::<{ N / 2 }, _>` in `from_fn_2`, which means that we will need to evaluate that constant during the const prop pass after inlining. Fixes #104396		2022-12-22 19:36:13 +01:00
..
src	Rollup merge of #105847 - compiler-errors:issue-104396, r=oli-obk	2022-12-22 19:36:13 +01:00
Cargo.toml	interpret: use Either over Result when it is not representing an error condition	2022-11-18 10:18:32 +01:00