about summary refs log tree commit diff
path: root/tests/ui/consts/promoted_size_overflow.rs
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2025-04-08 16:01:37 +0000
committerbors <bors@rust-lang.org>2025-04-08 16:01:37 +0000
commitd4f880f8ce832cd7560bb2f1ebc34f967055ffd7 (patch)
tree4800945779e7154bedca5c33143e4e7e33df7cd9 /tests/ui/consts/promoted_size_overflow.rs
parentf820b75feef00654924c9351a2faca8d34818339 (diff)
parentd35ad8d8362071410fd934dbb737379d736019ca (diff)
downloadrust-d4f880f8ce832cd7560bb2f1ebc34f967055ffd7.tar.gz
rust-d4f880f8ce832cd7560bb2f1ebc34f967055ffd7.zip
Auto merge of #138499 - lcnr:borrowck-typeck_root, r=oli-obk
borrowck typeck children together with their root

This introduces new cycle errors, even with `feature(inline_const_pat)` removed, see the `non-structural-match-types-cycle-err.rs` test.

The new cycle error happens as the layout of `async`-blocks relies on their `optimized_mir`. As that now depends on `mir_borrowck` of its typeck parent, computing the layout of an `async`-block during MIR building, e.g. when evaluating a named `const` pattern. I think there's currently no way to have a named const pattern whose type references an async block while being allowed? cc `@oli-obk` `@RalfJung`

I cannot think of other cases where we currently rely on the MIR of a typeck children while borrowchecking their parent. The crater run came back without any breakage. My work here will prevent any future features which rely on this as we'll get locked into borrowchecking them together as I continue to work on https://github.com/rust-lang/types-team/issues/129, cc `@rust-lang/types.`

r? compiler-errors
Diffstat (limited to 'tests/ui/consts/promoted_size_overflow.rs')
0 files changed, 0 insertions, 0 deletions