-
Notifications
You must be signed in to change notification settings - Fork 13.4k
nightly-20240112
regression: ICE: delayed span bug: inferring return types and opaque types do not mix well
#119916
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
C-bug
Category: This is a bug.
F-impl_trait_in_assoc_type
`#![feature(impl_trait_in_assoc_type)]`
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
requires-nightly
This issue requires a nightly compiler in some way.
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
nightly-2024-01-12
regression: ICE: delayed span bug: inferring return types and opaque types do not mix well
nightly-2024-01-12
regression: ICE: delayed span bug: inferring return types and opaque types do not mix wellnightly-20240112
regression: ICE: delayed span bug: inferring return types and opaque types do not mix well
#![feature(impl_trait_in_assoc_type)]
pub trait StreamConsumer {
type BarrierStream;
fn execute() -> Self::BarrierStream;
}
pub struct DispatchExecutor;
impl StreamConsumer for DispatchExecutor {
type BarrierStream = impl Sized;
fn execute() -> Self::BarrierStream {
|| -> _ {}
}
} @rustbot label -E-needs-mcve +S-has-mcve +F-impl_trait_in_assoc_type +requires-nightly |
compiler-errors
added a commit
to compiler-errors/rust
that referenced
this issue
Jan 17, 2024
…and-opaque-types-do-mix-sometimes, r=compiler-errors Don't ICE if TAIT-defining fn contains a closure with `_` in return type The `delay_span_bug` got added in rust-lang@0e82aae to reduce the amount of errors emitted for functions that have `_` in their return type, because inference doesn't apply to function items. But this logic shouldn't apply to closures, because their return types *can* be inferred. Fixes rust-lang#119916.
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Jan 17, 2024
…and-opaque-types-do-mix-sometimes, r=compiler-errors Don't ICE if TAIT-defining fn contains a closure with `_` in return type The `delay_span_bug` got added in rust-lang@0e82aae to reduce the amount of errors emitted for functions that have `_` in their return type, because inference doesn't apply to function items. But this logic shouldn't apply to closures, because their return types *can* be inferred. Fixes rust-lang#119916.
compiler-errors
added a commit
to compiler-errors/rust
that referenced
this issue
Jan 17, 2024
…and-opaque-types-do-mix-sometimes, r=compiler-errors Don't ICE if TAIT-defining fn contains a closure with `_` in return type The `delay_span_bug` got added in rust-lang@0e82aae to reduce the amount of errors emitted for functions that have `_` in their return type, because inference doesn't apply to function items. But this logic shouldn't apply to closures, because their return types *can* be inferred. Fixes rust-lang#119916.
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jan 18, 2024
Rollup merge of rust-lang#119975 - lukas-code:inferring-return-types-and-opaque-types-do-mix-sometimes, r=compiler-errors Don't ICE if TAIT-defining fn contains a closure with `_` in return type The `delay_span_bug` got added in rust-lang@0e82aae to reduce the amount of errors emitted for functions that have `_` in their return type, because inference doesn't apply to function items. But this logic shouldn't apply to closures, because their return types *can* be inferred. Fixes rust-lang#119916.
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
C-bug
Category: This is a bug.
F-impl_trait_in_assoc_type
`#![feature(impl_trait_in_assoc_type)]`
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
requires-nightly
This issue requires a nightly compiler in some way.
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Uh oh!
There was an error while loading. Please reload this page.
Code
https://github.com/risingwavelabs/risingwave
(not minimized yet)
https://github.com/risingwavelabs/risingwave/blob/7c3edb1ff2d64f9c0e50eacfca09ea5ce112ca2d/src/stream/src/executor/dispatch.rs#L382-L412
Error output
Bisect
searched nightlies: from nightly-2024-01-11 to nightly-2024-01-13
regressed nightly: nightly-2024-01-12
searched commit range: a2d9d73...62d7ed4
regressed commit: 65b323b
bisected with cargo-bisect-rustc v0.6.7
Host triple: aarch64-apple-darwin
Reproduce with:
The text was updated successfully, but these errors were encountered: