about summary refs log tree commit diff
path: root/tests/rustdoc-js-std/macro-print.js
diff options
context:
space:
mode:
authorMichael Goulet <michael@errs.io>2023-11-19 19:14:35 -0800
committerGitHub <noreply@github.com>2023-11-19 19:14:35 -0800
commit40a781b179be13cfbe89d0fdfd42632da6eb1e7b (patch)
tree5a0ba7d8e8084477e8fac380d99ee45ee7d82e0a /tests/rustdoc-js-std/macro-print.js
parente6a3ca0c657a6c37e309fd8c9f0cc41d13478e20 (diff)
parent488dcb7af3fc394ca438da2a9fe8a40dcae06948 (diff)
downloadrust-40a781b179be13cfbe89d0fdfd42632da6eb1e7b.tar.gz
rust-40a781b179be13cfbe89d0fdfd42632da6eb1e7b.zip
Rollup merge of #117994 - compiler-errors:throw-away-regions-in-coherence, r=lcnr
Ignore but do not assume region obligations from unifying headers in negative coherence

Partly addresses a FIXME that was added in #112875. Just as we can throw away the nested trait/projection obligations from unifying two impl headers, we can also just throw away the region obligations too.

I removed part of the FIXME that was incorrect, namely:
> Given that the only region constraints we get are involving inference regions in the root, it shouldn't matter, but still sus.

This is not true when unifying `fn(A)` and `for<'b> fn(&'b B)` which ends up with placeholder region outlives from non-root universes. I'm pretty sure this is okay, though it would be nice if we were to use them as assumptions. See the `explicit` revision of the test I committed, which still fails.

Fixes #117986

r? lcnr, feel free to reassign tho.
Diffstat (limited to 'tests/rustdoc-js-std/macro-print.js')
0 files changed, 0 insertions, 0 deletions