rust/tests/ui/macros/log_syntax-trace_macros-macro-locations.rs

// run-pass
// pretty-expanded FIXME #23616

#![feature(trace_macros, log_syntax)]

// make sure these macros can be used as in the various places that
// macros can occur.

// items
trace_macros!(false);
log_syntax!();

fn main() {

    // statements
    trace_macros!(false);
    log_syntax!();

    // expressions
    (trace_macros!(false),
     log_syntax!());
}
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			`// pretty-expanded FIXME #23616`

Remove ignore-fast that has cropped up 2014-04-03 15:02:50 -05:00			`#![feature(trace_macros, log_syntax)]`
syntax: allow `trace_macros!` and `log_syntax!` in item position. Previously trace_macros!(true) fn main() {} would complain about `trace_macros` being an expression macro in item position. This is a pointless limitation, because the macro is purely compile-time, with no runtime effect. (And similarly for log_syntax.) This also changes the behaviour of `trace_macros!` very slightly, it used to be equivalent to macro_rules! trace_macros { (true $($_x: tt)) => { true }; (false $($_x: tt)) => { false } } I.e. you could invoke it with arbitrary trailing arguments, which were ignored. It is changed to accept only exactly `true` or `false` (with no trailing arguments) and expands to `()`. 2014-03-18 07:14:08 -05:00
			`// make sure these macros can be used as in the various places that`
			`// macros can occur.`

			`// items`
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			`trace_macros!(false);`
			`log_syntax!();`
syntax: allow `trace_macros!` and `log_syntax!` in item position. Previously trace_macros!(true) fn main() {} would complain about `trace_macros` being an expression macro in item position. This is a pointless limitation, because the macro is purely compile-time, with no runtime effect. (And similarly for log_syntax.) This also changes the behaviour of `trace_macros!` very slightly, it used to be equivalent to macro_rules! trace_macros { (true $($_x: tt)) => { true }; (false $($_x: tt)) => { false } } I.e. you could invoke it with arbitrary trailing arguments, which were ignored. It is changed to accept only exactly `true` or `false` (with no trailing arguments) and expands to `()`. 2014-03-18 07:14:08 -05:00
			`fn main() {`

			`// statements`
			`trace_macros!(false);`
			`log_syntax!();`

			`// expressions`
			`(trace_macros!(false),`
			`log_syntax!());`
			`}`