-
Notifications
You must be signed in to change notification settings - Fork 13.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ICE: no errors encountered even though delay_span_bug
issued (regression on 2023-10-12)
#116684
Labels
C-bug
Category: This is a bug.
F-type_alias_impl_trait
`#[feature(type_alias_impl_trait)]`
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
requires-nightly
This issue requires a nightly compiler in some way.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
delay_span_bug
issued (regression on 2023-10-11)delay_span_bug
issued (regression on 2023-10-12)
I am minimizing this huge repo, I'll report when I have a result. |
https://github.com/matthiaskrgr/glacier2/blob/master/ices/108498.rs reproduces an ice with very similar stacktrace |
does the code compile before #114586 (i.e in nightly-10-09-2023)? |
Yes, it compiles in 2023-10-09.
…On Sat, Oct 14, 2023 at 7:10 AM Ali MJ Al-Nasrawy ***@***.***> wrote:
does the code compiles before #114586
<#114586> (i.e in
nightly-10-09-2023)?
—
Reply to this email directly, view it on GitHub
<#116684 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJBQZNPT5CQMXQ6D6WOAISTX7HC6ZAVCNFSM6AAAAAA56UVS5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRSGM3DMMRXGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
sorry, wrong date format. I meant 2023-09-10 |
Yes. 2023-09-10 is ok.
BTW, we are currently mainly using 2023-09-09 (
https://github.com/risingwavelabs/risingwave/blob/main/ci/rust-toolchain)
…On Sat, Oct 14, 2023 at 11:56 AM Ali MJ Al-Nasrawy ***@***.***> wrote:
Yes, it compiles in 2023-10-09.
sorry, wrong date format. I meant 2023-09-10
—
Reply to this email directly, view it on GitHub
<#116684 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJBQZNJSJHNBZUNXUYYWSUTX7IENVAVCNFSM6AAAAAA56UVS5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRSGU2TANJQHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@rustbot claim |
MCVE: #![feature(type_alias_impl_trait)]
fn rpit() -> impl Sized {}
pub type Tait = impl Sized;
pub fn foo() -> Box<dyn std::future::Future<Output = Tait>> {
Box::new(async {
let _out: Tait = rpit();
_out
})
} @rustbot label -E-needs-mcve |
Merged
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 18, 2023
Rollup merge of rust-lang#116879 - aliemjay:revert-opaque-bubble, r=oli-obk revert rust-lang#114586 Reverts rust-lang#114586. cc rust-lang#116877 (not closing until this gets a beta backport) fixes rust-lang#116684 fixes rust-lang#114586 (comment) r? `@oli-obk` or `@lcnr`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-bug
Category: This is a bug.
F-type_alias_impl_trait
`#[feature(type_alias_impl_trait)]`
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
requires-nightly
This issue requires a nightly compiler in some way.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Can be reproduced by:
Sorry for not having a minimal example yet.
Meta
rust version 1.75.0-nightly (475c71d 2023-10-11)
(A little background: We have a GHA to check whether build fails on latest nighty rust. It succeeds on 2023-10-11, but failed with ICE on 2023-10-12)
https://github.com/risingwavelabs/risingwave/actions/runs/6502231902/job/17660915782
Error output
Backtrace
The text was updated successfully, but these errors were encountered: