rust/src/test/compile-fail/recursion_limit.rs
Corey Farwell abd1cea145 Stop ignoring expected note/help messages in compiletest suite.
Original issue: https://github.com/rust-lang/rust/issues/21195

Relevant PR: https://github.com/rust-lang/rust/pull/30778

Prior to this commit, if a compiletest testcase included the text
"HELP:" or "NOTE:" (note the colons), then it would indicate to the
compiletest suite that we should verify "help" and "note" expected
messages.

This commit updates this check to also check "HELP" and "NOTE" (not the
absense of colons) so that we always verify "help" and "note" expected
messages.
2016-03-16 21:53:58 -04:00

58 lines
1.8 KiB
Rust

// Copyright 2014 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.
// Test that the recursion limit can be changed. In this case, we have
// deeply nested types that will fail the `Send` check by overflow
// when the recursion limit is set very low.
#![allow(dead_code)]
#![recursion_limit="10"]
macro_rules! link {
($id:ident, $t:ty) => {
enum $id { $id($t) }
}
}
link! { A, B }
link! { B, C }
link! { C, D }
link! { D, E }
link! { E, F }
link! { F, G }
link! { G, H }
link! { H, I }
link! { I, J }
link! { J, K }
link! { K, L }
link! { L, M }
link! { M, N }
enum N { N(usize) }
fn is_send<T:Send>() { }
fn main() {
is_send::<A>();
//~^ ERROR overflow evaluating
//~| NOTE consider adding a `#![recursion_limit="20"]` attribute to your crate
//~| NOTE required because it appears within the type `A`
//~| NOTE required because it appears within the type `B`
//~| NOTE required because it appears within the type `C`
//~| NOTE required because it appears within the type `D`
//~| NOTE required because it appears within the type `E`
//~| NOTE required because it appears within the type `F`
//~| NOTE required because it appears within the type `G`
//~| NOTE required because it appears within the type `H`
//~| NOTE required because it appears within the type `I`
//~| NOTE required because it appears within the type `J`
//~| NOTE required by `is_send`
}