rust/tests/ui/macros/pub-item-inside-macro.rs

// run-pass
// Issue #14660

// pretty-expanded FIXME #23616

mod bleh {
    macro_rules! foo {
        () => {
            pub fn bar() { }
        }
    }

    foo!();
}

fn main() {
    bleh::bar();
}
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 14:18:55 +02:00			`// run-pass`
Forbid `pub mymacro!();` It's not clear what this means, because a macro in item position can expand to zero or more items. For now we disallow it, which is technically a [breaking-change] but is landing without an RFC. The `pub` keyword previously had no effect, which seems quite unintended. Fixes #18317. Fixes #14660. 2015-02-12 20:43:57 -08:00			`// Issue #14660`

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 13:13:15 -07:00			`// pretty-expanded FIXME #23616`

Forbid `pub mymacro!();` It's not clear what this means, because a macro in item position can expand to zero or more items. For now we disallow it, which is technically a [breaking-change] but is landing without an RFC. The `pub` keyword previously had no effect, which seems quite unintended. Fixes #18317. Fixes #14660. 2015-02-12 20:43:57 -08:00			`mod bleh {`
			`macro_rules! foo {`
			`() => {`
			`pub fn bar() { }`
			`}`
			`}`

			`foo!();`
			`}`

			`fn main() {`
			`bleh::bar();`
			`}`