rust/tests/ui/proc-macro/issue-59191-replace-root-with-fn.rs

// Test that using a macro to replace the entire crate tree with a non-'mod' item errors out nicely.
// `issue_59191::no_main` replaces whatever's passed in with `fn main() {}`.

//@ edition:2018
//@ proc-macro: issue-59191.rs
//@ needs-unwind (affects error output)

#![feature(custom_inner_attributes)]
#![issue_59191::no_main]
#![issue_59191::no_main]

//~? ERROR `#[panic_handler]` function required, but not found
//~? ERROR unwinding panics are not supported without std
Add tests for issue 59191 2020-02-01 18:07:26 -08:00			`// Test that using a macro to replace the entire crate tree with a non-'mod' item errors out nicely.`
			// `issue_59191::no_main` replaces whatever's passed in with `fn main() {}`.
expand: Turn `ast::Crate` into a first class expansion target And stop creating a fake `mod` item for the crate root when expanding a crate. 2021-10-17 19:32:34 +03:00
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ edition:2018`
Update tests to use new proc-macro header 2024-11-24 17:37:25 -08:00			`//@ proc-macro: issue-59191.rs`
Inject `compiler_builtins` during postprocessing rather than via AST `compiler_builtins` is currently injected as `extern crate compiler_builtins as _`. This has made gating via diagnostics difficult because it appears in the crate graph as a non-private dependency, and there isn't an easy way to differentiate between the injected AST and user-specified `extern crate compiler_builtins`. Resolve this by injecting `compiler_builtins` during postprocessing rather than early in the AST. Most of the time this isn't even needed because it shows up in `std` or `core`'s crate graph, but injection is still needed to ensure `#![no_core]` works correctly. A similar change was attempted at [1] but this encountered errors building `proc_macro` and `rustc-std-workspace-std`. Similar failures showed up while working on this patch, which were traced back to `compiler_builtins` showing up in the graph twice (once via dependency and once via injection). This is resolved by not injecting if a `#![compiler_builtins]` crate already exists. [1]: https://github.com/rust-lang/rust/pull/113634 2025-01-29 23:54:15 +00:00			`//@ needs-unwind (affects error output)`
expand: Turn `ast::Crate` into a first class expansion target And stop creating a fake `mod` item for the crate root when expanding a crate. 2021-10-17 19:32:34 +03:00
Add tests for issue 59191 2020-02-01 18:07:26 -08:00			`#![feature(custom_inner_attributes)]`
			`#![issue_59191::no_main]`
expand: Turn `ast::Crate` into a first class expansion target And stop creating a fake `mod` item for the crate root when expanding a crate. 2021-10-17 19:32:34 +03:00			`#![issue_59191::no_main]`
compiletest: Require `//~` annotations even if `error-pattern` is specified 2025-03-29 02:41:32 +03:00
			//~? ERROR `#[panic_handler]` function required, but not found
			`//~? ERROR unwinding panics are not supported without std`