rust/src/test/compile-fail/issue-21221-1.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

102 lines
2.7 KiB
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.
mod mul1 {
pub trait Mul {}
}
mod mul2 {
pub trait Mul {}
}
mod mul3 {
enum Mul {
Yes,
No
}
}
mod mul4 {
type Mul = String;
}
mod mul5 {
struct Mul{
left_term: u32,
right_term: u32
}
}
#[derive(Debug)]
struct Foo;
// When we comment the next line:
//use mul1::Mul;
// BEFORE, we got the following error for the `impl` below:
// error: use of undeclared trait name `Mul` [E0405]
// AFTER, we get this message:
// error: trait `Mul` is not in scope.
// help: ...
// help: you can import several candidates into scope (`use ...;`):
// help: `mul1::Mul`
// help: `mul2::Mul`
// help: `std::ops::Mul`
impl Mul for Foo {
//~^ ERROR trait `Mul` is not in scope
//~| HELP `mul1::Mul`
//~| HELP `mul2::Mul`
//~| HELP `std::ops::Mul`
//~| HELP run `rustc --explain E0405` to see a detailed explanation
//~| HELP you can import several candidates into scope (`use ...;`):
}
// BEFORE, we got:
// error: use of undeclared type name `Mul` [E0412]
// AFTER, we get:
// error: type name `Mul` is not in scope. Maybe you meant:
// help: ...
// help: you can import several candidates into scope (`use ...;`):
// help: `mul1::Mul`
// help: `mul2::Mul`
// help: `mul3::Mul`
// help: `mul4::Mul`
// help: and 2 other candidates
fn getMul() -> Mul {
//~^ ERROR type name `Mul` is undefined or not in scope
//~| HELP `mul1::Mul`
//~| HELP `mul2::Mul`
//~| HELP `mul3::Mul`
//~| HELP `mul4::Mul`
//~| HELP and 2 other candidates
//~| HELP run `rustc --explain E0412` to see a detailed explanation
//~| HELP you can import several candidates into scope (`use ...;`):
}
// Let's also test what happens if the trait doesn't exist:
impl ThisTraitReallyDoesntExistInAnyModuleReally for Foo {
//~^ ERROR trait `ThisTraitReallyDoesntExistInAnyModuleReally` is not in scope
//~^^ HELP run `rustc --explain E0405` to see a detailed explanation
//~^^^ HELP no candidates by the name of `ThisTraitReallyDoesntExistInAnyModuleReally` found
}
// Let's also test what happens if there's just one alternative:
impl Div for Foo {
//~^ ERROR trait `Div` is not in scope
//~| HELP `use std::ops::Div;`
//~| HELP run `rustc --explain E0405` to see a detailed explanation
}
fn main() {
let foo = Foo();
println!("Hello, {:?}!", foo);
}