Dylan DPC 6da62a40f2 Rollup merge of #110614 - compiler-errors:new-solver-overflow-response, r=lcnr ... Clear response values for overflow in new solver When we have an overflow, return a trivial query response. This fixes an ICE with the code described in #110544: ```rust trait Trait {} struct W<T>(T); impl<T, U> Trait for W<(W<T>, W<U>)> where W<T>: Trait, W<U>: Trait, {} fn impls<T: Trait>() {} fn main() { impls::<W<_>>() } ``` Where, while proving `W<?0>: Trait`, we overflow but still apply the query response of `?0 = (W<?1>, W<?2>)`. Then while re-processing the query to validate that our evaluation result was stable, we get a different query response that looks like `?1 = (W<?3>, W<?4>), ?2 = (W<?5>, W<?6>)`, and so we trigger the ICE. Also, by returning a trivial query response we also avoid the infinite-loop/OOM behavior of the old solver. r? ``@lcnr``		2023-04-29 11:27:54 +05:30
..
src	Rollup merge of #110614 - compiler-errors:new-solver-overflow-response, r=lcnr	2023-04-29 11:27:54 +05:30
Cargo.toml	drop unused deps, gate libc under unix for one crate	2023-04-22 15:22:21 +03:00
messages.ftl	Simplify message paths	2023-03-11 22:51:57 +01:00