diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2023-06-09 16:29:02 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-06-09 16:29:02 +0200 |
| commit | 4ef72570189401dee5b148fd423b36cfd37fa3f7 (patch) | |
| tree | faf1c9d11e60fd3df5941ae1679293cd7d0e8d87 /x.py | |
| parent | f83c8e43170da30341d4d4cfcdf7039dc7f987d3 (diff) | |
| parent | d5e25d40c969009d0f40cbf6280339f2839e19c4 (diff) | |
| download | rust-4ef72570189401dee5b148fd423b36cfd37fa3f7.tar.gz rust-4ef72570189401dee5b148fd423b36cfd37fa3f7.zip | |
Rollup merge of #112442 - compiler-errors:next-solver-deduplicate-region-constraints, r=lcnr
Deduplicate identical region constraints in new solver the new solver doesn't track whether we've already proven a goal like the fulfillment context's obligation forest does, so we may be instantiating a canonical response (and specifically, its nested region obligations) quite a few times. This may lead to exponentially gathering up identical region constraints for things like auto traits, so let's deduplicate region constraints when in `compute_external_query_constraints`. r? ``@lcnr``
Diffstat (limited to 'x.py')
0 files changed, 0 insertions, 0 deletions