rust/tests/ui/force-inlining/gate.stderr

error[E0658]: use of an internal attribute
  --> $DIR/gate.rs:4:1
   |
LL | #[rustc_force_inline]
   | ^^^^^^^^^^^^^^^^^^^^^
   |
   = help: add `#![feature(rustc_attrs)]` to the crate attributes to enable
   = note: the `#[rustc_force_inline]` attribute is an internal implementation detail that will never be stable
   = note: `#[rustc_force_inline]` forces a free function to be inlined

error[E0658]: use of an internal attribute
  --> $DIR/gate.rs:11:1
   |
LL | #[rustc_force_inline = "the test requires it"]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: add `#![feature(rustc_attrs)]` to the crate attributes to enable
   = note: the `#[rustc_force_inline]` attribute is an internal implementation detail that will never be stable
   = note: `#[rustc_force_inline]` forces a free function to be inlined

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0658`.
refactor `AttributeGate` and `rustc_attr!` to emit notes during feature checking 2025-05-18 18:35:13 +02:00			`error[E0658]: use of an internal attribute`
mir_transform: implement forced inlining Adds `#[rustc_force_inline]` which is similar to always inlining but reports an error if the inlining was not possible, and which always attempts to inline annotated items, regardless of optimisation levels. It can only be applied to free functions to guarantee that the MIR inliner will be able to resolve calls. 2024-09-23 18:46:23 +01:00			`--> $DIR/gate.rs:4:1`
			`\|`
			`LL \| #[rustc_force_inline]`
			`\| ^^^^^^^^^^^^^^^^^^^^^`
			`\|`
			= help: add `#![feature(rustc_attrs)]` to the crate attributes to enable
refactor `AttributeGate` and `rustc_attr!` to emit notes during feature checking 2025-05-18 18:35:13 +02:00			= note: the `#[rustc_force_inline]` attribute is an internal implementation detail that will never be stable
			= note: `#[rustc_force_inline]` forces a free function to be inlined
mir_transform: implement forced inlining Adds `#[rustc_force_inline]` which is similar to always inlining but reports an error if the inlining was not possible, and which always attempts to inline annotated items, regardless of optimisation levels. It can only be applied to free functions to guarantee that the MIR inliner will be able to resolve calls. 2024-09-23 18:46:23 +01:00
refactor `AttributeGate` and `rustc_attr!` to emit notes during feature checking 2025-05-18 18:35:13 +02:00			`error[E0658]: use of an internal attribute`
			`--> $DIR/gate.rs:11:1`
mir_transform: implement forced inlining Adds `#[rustc_force_inline]` which is similar to always inlining but reports an error if the inlining was not possible, and which always attempts to inline annotated items, regardless of optimisation levels. It can only be applied to free functions to guarantee that the MIR inliner will be able to resolve calls. 2024-09-23 18:46:23 +01:00			`\|`
			`LL \| #[rustc_force_inline = "the test requires it"]`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
			`\|`
			= help: add `#![feature(rustc_attrs)]` to the crate attributes to enable
refactor `AttributeGate` and `rustc_attr!` to emit notes during feature checking 2025-05-18 18:35:13 +02:00			= note: the `#[rustc_force_inline]` attribute is an internal implementation detail that will never be stable
			= note: `#[rustc_force_inline]` forces a free function to be inlined
mir_transform: implement forced inlining Adds `#[rustc_force_inline]` which is similar to always inlining but reports an error if the inlining was not possible, and which always attempts to inline annotated items, regardless of optimisation levels. It can only be applied to free functions to guarantee that the MIR inliner will be able to resolve calls. 2024-09-23 18:46:23 +01:00
			`error: aborting due to 2 previous errors`

			For more information about this error, try `rustc --explain E0658`.