You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ICE on rustc 1.41.0-nightly (25d8a9494 2019-11-29) running on x86_64-apple-darwin #66958
Certainly! Although it is not the best stacktrace I have ever seen.
thread 'rustc' panicked at 'called `Option::unwrap()` on a `None` value', /rustc/25d8a9494ca6d77361e47c1505ecf640b168819e/src/libcore/macros/mod.rs:15:40
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: rustc 1.41.0-nightly (25d8a9494 2019-11-29) running on x86_64-apple-darwin
note: compiler flags: -C debuginfo=2 -C incremental --crate-type bin
note: some of the compiler flags provided by cargo are hidden
error: could not compile `pixurs`.
To learn more, run the command again with --verbose.
The problem seems to be a partial move of self together with async together with a generic type S (if we replace S by String for example, rust will complain as well and no ICE).
If we remove the async rust will complain:
error[E0382]: use of moved value: `self`
--> src/main.rs:9:20
|
8 | Self::partial(self.1);
| ------ value moved here
9 | Self::full(self);
| ^^^^ value used here after partial move
|
= note: move occurs because `self.1` has type `S`, which does not implement the `Copy` trait
Activity
jonas-schievink commentedon Dec 2, 2019
Can you post the ICE message and backtrace?
maghoff commentedon Dec 2, 2019
Certainly! Although it is not the best stacktrace I have ever seen.
Backtrace:
hellow554 commentedon Dec 3, 2019
Backtrace:
hellow554 commentedon Dec 3, 2019
hellow554 commentedon Dec 3, 2019
I think I have a clue here:
First the code:
The problem seems to be a partial move of
selftogether with async together with a generic typeS(if we replaceSbyStringfor example, rust will complain as well and no ICE).If we remove the
asyncrust will complain:@rustbot modify labels: +A-async-await -E-needs-mcve +E-needs-bisection
hellow554 commentedon Dec 3, 2019
Regression in 861e96f #66567 cc @estebank
@rustbot modify labels: -E-needs-bisection
pnkfelix commentedon Dec 5, 2019
triage: has PR. P-high, removing nomination.
Do not ICE on async fn with non-Copy infered type arg
Rollup merge of rust-lang#67004 - estebank:issue-66958, r=eddyb
Rollup merge of rust-lang#67004 - estebank:issue-66958, r=eddyb
Auto merge of #67004 - estebank:issue-66958, r=eddyb