ICE cause by tokio::spawn a async function return future opaque type #68477
Labels
A-async-await
Area: Async & Await
A-const-eval
Area: Constant evaluation, covers all const contexts (static, const fn, ...)
A-impl-trait
Area: `impl Trait`. Universally / existentially quantified anonymous types with static dispatch.
AsyncAwait-Polish
Async-await issues that are part of the "polish" area
AsyncAwait-Triaged
Async-await issues that have been triaged during a working group meeting.
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
P-high
High priority
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
The ICE cause by
cargo check
, seems happened in multiple locations. One of the cause is when callingtokio::spawn
function.I don't know how to reproduce this problem in minimal example, but the faulty code in my project comes from here
https://github.com/ShisoftResearch/bifrost/blob/f67c57209dd15072a2868f46c1d26cd356caafae/src/raft/mod.rs#L631
Expecting the code to compile or providing reason for the failure. Instead, the compile just crashed.
This problem appears on both MacOS and Linux
Meta
rustc 1.42.0-nightly (5e8897b 2020-01-21)
binary: rustc
commit-hash: 5e8897b
commit-date: 2020-01-21
host: x86_64-unknown-linux-gnu
release: 1.42.0-nightly
LLVM version: 9.0
tokio 0.2.10
Backtrace:
The text was updated successfully, but these errors were encountered: