Oli Scherer f394bb57bb Always use const param envs for const eval. ... Nothing else makes sense, and there is no "danger" in doing so, as it only does something if there are const bounds, which are unstable. This used to happen implicitly via the inferctxt before, which was much more fragile.		2021-11-29 21:19:50 +08:00
..
error.rs	use matches!() macro in more places	2021-11-06 16:13:14 +01:00
eval_queries.rs	Always use const param envs for const eval.	2021-11-29 21:19:50 +08:00
fn_queries.rs	use matches!() macro in more places	2021-11-06 16:13:14 +01:00
machine.rs	Remove is_const_fn in find_mir_or_eval_fn	2021-10-27 07:21:28 +01:00
mod.rs	Rename rustc_mir to rustc_const_eval.	2021-09-07 20:46:26 +02:00