diff options
| author | Matthias Krüger <476013+matthiaskrgr@users.noreply.github.com> | 2025-09-24 20:34:19 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-24 20:34:19 +0200 |
| commit | 315053891196d8514c43d62792b2e0bb76ddcbc0 (patch) | |
| tree | e727f633681fb15d1a03222f64fb8eaaab878256 /tests/rustdoc-js-std/parser-tuple.js | |
| parent | 15283f6fe95e5b604273d13a428bab5fc0788f5a (diff) | |
| parent | 3378997867a9501beb3137f1ae508aadf1b9fc4b (diff) | |
| download | rust-315053891196d8514c43d62792b2e0bb76ddcbc0.tar.gz rust-315053891196d8514c43d62792b2e0bb76ddcbc0.zip | |
Rollup merge of #146711 - lcnr:fix-placeholder-ice, r=lqd
fix 2 borrowck issues
fixes https://github.com/rust-lang/rust/issues/146467 cc ``@amandasystems``
our understanding here is as follows: region constraints from computing implied bounds gets `ConstraintCategory::Internal`. If there's a higher-ranked subtyping errors while computing implied bounds we then ended up with only `ConstraintCategory::Internal` and `ConstraintCategory::OutlivesUnnameablePlaceholder(_)` constraints.
The path was something like
- `'placeholderU2: 'placeholderU1` (`Internal`)
- `'placeholderU1: 'static` (`OutlivesUnnameablePlaceholder('placeholderU2)`)
It's generally somewhat subtle here as ideally relating placeholders doesn't introduce `'static` constraints. Relating the placeholders themselves will always error regardless, cc https://github.com/rust-lang/rust/pull/142623.
---
separately fixes https://github.com/rust-lang/rust/pull/145925#issuecomment-3303733357 by updating the location for deferred closure requirements inside of promoteds. I am not updating their category as doing so is 1) effort and 2) imo actually undesirable :thinking: see the comments in `TypeChecker::check_promoted` cc ``@lqd``
r? lqd
Diffstat (limited to 'tests/rustdoc-js-std/parser-tuple.js')
0 files changed, 0 insertions, 0 deletions