rust/src/test/ui/run-pass/issues/issue-8709.rs

// 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.


macro_rules! sty {
    ($t:ty) => (stringify!($t))
}

macro_rules! spath {
    ($t:path) => (stringify!($t))
}

fn main() {
    assert_eq!(sty!(isize), "isize");
    assert_eq!(spath!(std::option), "std::option");
}
Correctly stringify! types and paths inside macros Closes #8709 2014-07-19 09:59:44 +00:00			`// 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.`

rustdoc: Replace no-pretty-expanded with pretty-expanded Now that features must be declared expanded source often does not compile. This adds 'pretty-expanded' to a bunch of test cases that still work. 2015-03-22 20:13:15 +00:00
Modernize macro_rules! invocations macro_rules! is like an item that defines a macro. Other items don't have a trailing semicolon, or use a paren-delimited body. If there's an argument for matching the invocation syntax, e.g. parentheses for an expr macro, then I think that applies more strongly to the inner delimiters on the LHS, wrapping the individual argument patterns. 2015-01-02 22:44:21 +00:00			`macro_rules! sty {`
Correctly stringify! types and paths inside macros Closes #8709 2014-07-19 09:59:44 +00:00			`($t:ty) => (stringify!($t))`
Modernize macro_rules! invocations macro_rules! is like an item that defines a macro. Other items don't have a trailing semicolon, or use a paren-delimited body. If there's an argument for matching the invocation syntax, e.g. parentheses for an expr macro, then I think that applies more strongly to the inner delimiters on the LHS, wrapping the individual argument patterns. 2015-01-02 22:44:21 +00:00			`}`
Correctly stringify! types and paths inside macros Closes #8709 2014-07-19 09:59:44 +00:00
Modernize macro_rules! invocations macro_rules! is like an item that defines a macro. Other items don't have a trailing semicolon, or use a paren-delimited body. If there's an argument for matching the invocation syntax, e.g. parentheses for an expr macro, then I think that applies more strongly to the inner delimiters on the LHS, wrapping the individual argument patterns. 2015-01-02 22:44:21 +00:00			`macro_rules! spath {`
Correctly stringify! types and paths inside macros Closes #8709 2014-07-19 09:59:44 +00:00			`($t:path) => (stringify!($t))`
Modernize macro_rules! invocations macro_rules! is like an item that defines a macro. Other items don't have a trailing semicolon, or use a paren-delimited body. If there's an argument for matching the invocation syntax, e.g. parentheses for an expr macro, then I think that applies more strongly to the inner delimiters on the LHS, wrapping the individual argument patterns. 2015-01-02 22:44:21 +00:00			`}`
Correctly stringify! types and paths inside macros Closes #8709 2014-07-19 09:59:44 +00:00
			`fn main() {`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-26 00:06:52 +00:00			`assert_eq!(sty!(isize), "isize");`
librustc: Always parse `macro!()`/`macro![]` as expressions if not followed by a semicolon. This allows code like `vec![1i, 2, 3].len();` to work. This breaks code that uses macros as statements without putting semicolons after them, such as: fn main() { ... assert!(a == b) assert!(c == d) println(...); } It also breaks code that uses macros as items without semicolons: local_data_key!(foo) fn main() { println("hello world") } Add semicolons to fix this code. Those two examples can be fixed as follows: fn main() { ... assert!(a == b); assert!(c == d); println(...); } local_data_key!(foo); fn main() { println("hello world") } RFC #378. Closes #18635. [breaking-change] 2014-11-14 17:18:10 +00:00			`assert_eq!(spath!(std::option), "std::option");`
Correctly stringify! types and paths inside macros Closes #8709 2014-07-19 09:59:44 +00:00			`}`