6353e30bb2
This flag is a debugging measure designed to detect cases where we start a snapshot, create type variables, register obligations involving those type variables in the fulfillment cx, and then have to unroll the snapshot, leaving "dangling type variables" behind. HOWEVER, in some cases the flag is wrong. In particular, we sometimes create a "mini-fulfilment-cx" in which we enroll obligations. As long as this fulfillment cx is fully drained before we return, this is not a problem, as there won't be any escaping obligations in the main cx. So we add a fn to save/restore the flag.
21 lines
785 B
Rust
21 lines
785 B
Rust
// Copyright 2016 The Rust Project Developers. See the COPYRIGHT
|
|
// file at the top-level directory of this distribution and at
|
|
// http://rust-lang.org/COPYRIGHT.
|
|
//
|
|
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
// option. This file may not be copied, modified, or distributed
|
|
// except according to those terms.
|
|
|
|
// Regression test for #36053. ICE was caused due to obligations
|
|
// being added to a special, dedicated fulfillment cx during
|
|
// a probe.
|
|
|
|
use std::iter::once;
|
|
fn main() {
|
|
once::<&str>("str").fuse().filter(|a: &str| true).count();
|
|
//~^ ERROR no method named `count`
|
|
//~| ERROR E0281
|
|
//~| ERROR E0281
|
|
}
|