Matthias Krüger 3b6593a0b4 Rollup merge of #107103 - compiler-errors:new-solver-evaluate_obligation, r=lcnr ... Use new solver in `evaluate_obligation` query (when new solver is enabled) (only when `-Ztrait-solver=next`, of course) ... Does this make sense? It seems to me like it should be reasonable, but maybe there's some reason why this is a bad idea. r? ``@lcnr`` Needs a perf run because I guess this `solver == TraitSolver::Next` check is on a hot path.		2023-01-28 05:20:16 +01:00
..
type_op	Simplify some canonical type alias names	2023-01-03 01:16:10 +00:00
dropck_outlives.rs	Introduce GeneratorWitnessMIR.	2023-01-27 18:58:44 +00:00
evaluate_obligation.rs	Use now solver in evaluate_obligation	2023-01-27 17:53:07 +00:00
method_autoderef.rs	mv compiler to compiler/	2020-08-30 18:45:07 +03:00
mod.rs	Move some outlives bounds things from rustc_trait_selection to rustc_typeck	2021-10-15 12:14:19 -04:00
normalize.rs	Pacify tidy.	2023-01-27 22:01:25 +00:00