diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-02-20 19:35:40 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-20 19:35:40 +0100 |
| commit | d43fd29bf2d0133b729d2c2187d195915b8cacfd (patch) | |
| tree | f39c9a2eb7c5e15b76b90281f48d82cc20ae377b /compiler/rustc_interface/src/errors.rs | |
| parent | 3099a7931ab6b04874b5d8b9bcabddd5478cf4cf (diff) | |
| parent | 994d55158dcfe0b1b299591bb552af14c63c6e60 (diff) | |
| download | rust-d43fd29bf2d0133b729d2c2187d195915b8cacfd.tar.gz rust-d43fd29bf2d0133b729d2c2187d195915b8cacfd.zip | |
Rollup merge of #121322 - compiler-errors:next-solver-fulfillment-ice, r=lcnr
Don't ICE when hitting overflow limit in fulfillment loop in next solver As the title says, let's not ICE when hitting the overflow limit in fulfill. On the other hand, we don't want to treat these as true errors, since it means that whether something is considered a true error or an ambiguity is dependent on overflow handling in the solver, which seems not worth it. Now that we use the presence of true errors in fulfillment for implicit negative coherence, we especially don't want to tie together coherence and overflow. I guess I could also drain these errors out of fulfillment and put them into some `ambiguities` storage so we could return them in `select_all_or_error` without having to re-process them every time we call `select_where_possible`. Let me know if that's desired. r? lcnr
Diffstat (limited to 'compiler/rustc_interface/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
