rust/tests/ui/macros/issue-8709.rs

// run-pass

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");
}
Add `// run-pass` annotations to all the tests under `ui/run-pass/`. (I may have accidentally added it to some auxilliary crates as well; my emacs-macro-based methodology was pretty crude.) 2018-08-30 07:18:55 -05:00			`// run-pass`
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 15:13:15 -05: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 16:44:21 -06:00			`macro_rules! sty {`
Correctly stringify! types and paths inside macros Closes #8709 2014-07-19 04:59:44 -05: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 16:44:21 -06:00			`}`
Correctly stringify! types and paths inside macros Closes #8709 2014-07-19 04:59:44 -05: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 16:44:21 -06:00			`macro_rules! spath {`
Correctly stringify! types and paths inside macros Closes #8709 2014-07-19 04:59:44 -05: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 16:44:21 -06:00			`}`
Correctly stringify! types and paths inside macros Closes #8709 2014-07-19 04:59:44 -05:00
			`fn main() {`
Mass rename uint/int to usize/isize Now that support has been removed, all lingering use cases are renamed. 2015-03-25 19:06:52 -05: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 11:18:10 -06:00			`assert_eq!(spath!(std::option), "std::option");`
Correctly stringify! types and paths inside macros Closes #8709 2014-07-19 04:59:44 -05:00			`}`