diff options
| author | bors <bors@rust-lang.org> | 2023-07-14 21:14:30 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-07-14 21:14:30 +0000 |
| commit | ad963232d9b987d66a6f8e6ec4141f672b8b9900 (patch) | |
| tree | 1b2b8e73859396febee569eb305720626c9eb62c /tests/rustdoc/ensure-src-link.rs | |
| parent | 3b55d2385a85271808f301c4000c7ca178bccc41 (diff) | |
| parent | 1ef85d82e0904367a603f97c100bcbb23f8ce2ff (diff) | |
| download | rust-ad963232d9b987d66a6f8e6ec4141f672b8b9900.tar.gz rust-ad963232d9b987d66a6f8e6ec4141f672b8b9900.zip | |
Auto merge of #113471 - compiler-errors:new-solver-norm-escaping, r=lcnr
Allow escaping bound vars during `normalize_erasing_regions` in new solver Add `AllowEscapingBoundVars` to `deeply_normalize`, and use it in the new solver in the `query_normalize` routine. Ideally, we'd make all `query_normalize` calls handle pass in `AllowEscapingBoundVars` individually, because really the only `query_normalize` call that needs `AllowEscapingBoundVars::Yes` is the one in `try_normalize_generic_arg_after_erasing_regions`, but I think that's kind of overkill. I am happy to be convinced otherwise, though. r? `@lcnr`
Diffstat (limited to 'tests/rustdoc/ensure-src-link.rs')
0 files changed, 0 insertions, 0 deletions