rust/src/test/compile-fail/macro-backtrace-invalid-internals.rs
Sean Patrick Santos b4bbf3a88d Fix ICE that occurs when an associated const is ambiguous.
Also change several error messages to refer to "items" rather than
"methods", since associated items that require resolution during type
checking are not always methods.
2015-05-13 18:10:01 -06:00

58 lines
1.5 KiB
Rust

// Copyright 2015 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.
// Macros in statement vs expression position handle backtraces differently.
macro_rules! fake_method_stmt { //~ NOTE in expansion of
() => {
1.fake() //~ ERROR no method named `fake` found
}
}
macro_rules! fake_field_stmt { //~ NOTE in expansion of
() => {
1.fake //~ ERROR no field with that name
}
}
macro_rules! fake_anon_field_stmt { //~ NOTE in expansion of
() => {
(1).0 //~ ERROR type was not a tuple
}
}
macro_rules! fake_method_expr { //~ NOTE in expansion of
() => {
1.fake() //~ ERROR no method named `fake` found
}
}
macro_rules! fake_field_expr {
() => {
1.fake
}
}
macro_rules! fake_anon_field_expr {
() => {
(1).0
}
}
fn main() {
fake_method_stmt!(); //~ NOTE expansion site
fake_field_stmt!(); //~ NOTE expansion site
fake_anon_field_stmt!(); //~ NOTE expansion site
let _ = fake_method_expr!(); //~ NOTE expansion site
let _ = fake_field_expr!(); //~ ERROR no field with that name
let _ = fake_anon_field_expr!(); //~ ERROR type was not a tuple
}