-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Closed
Labels
C-bugCategory: This is a bug.Category: This is a bug.I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️P-highHigh priorityHigh priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.Performance or correctness regression from stable to beta.
Description
New ICE discovered (in itertools' test suite):
thread 'rustc' panicked at 'region_obligations not empty: [
(
NodeId(
0
),
RegionObligation(sub_region='_#60r, sup_type=u8)
)
]', /checkout/src/librustc/infer/mod.rs:1160:8
(Note, the issue has been worked around in itertools, to keep CI green)
Code to reproduce
//! ```cargo
//! [dependencies]
//! itertools = "=0.7.2"
//! ```
extern crate itertools;
use itertools::Itertools;
fn equal_combinations_2(a: Vec<u8>) {
a.iter().cloned().tuple_combinations::<(_, _)>();
}
Implementation links for tuple_combinations:
Full error
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.23.0-nightly (d0f8e2913 2017-11-16) running on x86_64-unknown-linux-gnu
thread 'rustc' panicked at 'region_obligations not empty: [
(
NodeId(
0
),
RegionObligation(sub_region='_#60r, sup_type=u8)
)
]', /checkout/src/librustc/infer/mod.rs:1160:8
mtak-
Metadata
Metadata
Assignees
Labels
C-bugCategory: This is a bug.Category: This is a bug.I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️P-highHigh priorityHigh priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-betaPerformance or correctness regression from stable to beta.Performance or correctness regression from stable to beta.