rust/tests/ui/feature-gates/feature-gate-unsafe_pin_internals.stderr

error: the feature `unsafe_pin_internals` is internal to the compiler or standard library
  --> $DIR/feature-gate-unsafe_pin_internals.rs:3:12
   |
LL | #![feature(unsafe_pin_internals)]
   |            ^^^^^^^^^^^^^^^^^^^^
   |
   = note: using it is strongly discouraged
note: the lint level is defined here
  --> $DIR/feature-gate-unsafe_pin_internals.rs:2:11
   |
LL | #![forbid(internal_features, unsafe_code)]
   |           ^^^^^^^^^^^^^^^^^

error: aborting due to 1 previous error
Add `internal_features` lint It lints against features that are inteded to be internal to the compiler and standard library. Implements MCP #596. We allow `internal_features` in the standard library and compiler as those use many features and this _is_ the standard library from the "internal to the compiler and standard library" after all. Marking some features as internal wasn't exactly the most scientific approach, I just marked some mostly obvious features. While there is a categorization in the macro, it's not very well upheld (should probably be fixed in another PR). We always pass `-Ainternal_features` in the testsuite About 400 UI tests and several other tests use internal features. Instead of throwing the attribute on each one, just always allow them. There's nothing wrong with testing internal features^^ 2023-03-09 14:54:53 -06:00			error: the feature `unsafe_pin_internals` is internal to the compiler or standard library
Mark `unsafe_pin_internals` as `incomplete`. This thus still makes it technically possible to enable the feature, and thus to trigger UB without `unsafe`, but this is fine since incomplete features are known to be potentially unsound (labelled "may not be safe"). This follows from the discussion at https://github.com/rust-lang/rust/pull/93176#discussion_r799413561 2022-01-23 18:34:46 -06:00			`--> $DIR/feature-gate-unsafe_pin_internals.rs:3:12`
			`\|`
			`LL \| #![feature(unsafe_pin_internals)]`
			`\| ^^^^^^^^^^^^^^^^^^^^`
			`\|`
Add `internal_features` lint It lints against features that are inteded to be internal to the compiler and standard library. Implements MCP #596. We allow `internal_features` in the standard library and compiler as those use many features and this _is_ the standard library from the "internal to the compiler and standard library" after all. Marking some features as internal wasn't exactly the most scientific approach, I just marked some mostly obvious features. While there is a categorization in the macro, it's not very well upheld (should probably be fixed in another PR). We always pass `-Ainternal_features` in the testsuite About 400 UI tests and several other tests use internal features. Instead of throwing the attribute on each one, just always allow them. There's nothing wrong with testing internal features^^ 2023-03-09 14:54:53 -06:00			`= note: using it is strongly discouraged`
Mark `unsafe_pin_internals` as `incomplete`. This thus still makes it technically possible to enable the feature, and thus to trigger UB without `unsafe`, but this is fine since incomplete features are known to be potentially unsound (labelled "may not be safe"). This follows from the discussion at https://github.com/rust-lang/rust/pull/93176#discussion_r799413561 2022-01-23 18:34:46 -06:00			`note: the lint level is defined here`
			`--> $DIR/feature-gate-unsafe_pin_internals.rs:2:11`
			`\|`
Add `internal_features` lint It lints against features that are inteded to be internal to the compiler and standard library. Implements MCP #596. We allow `internal_features` in the standard library and compiler as those use many features and this _is_ the standard library from the "internal to the compiler and standard library" after all. Marking some features as internal wasn't exactly the most scientific approach, I just marked some mostly obvious features. While there is a categorization in the macro, it's not very well upheld (should probably be fixed in another PR). We always pass `-Ainternal_features` in the testsuite About 400 UI tests and several other tests use internal features. Instead of throwing the attribute on each one, just always allow them. There's nothing wrong with testing internal features^^ 2023-03-09 14:54:53 -06:00			`LL \| #![forbid(internal_features, unsafe_code)]`
			`\| ^^^^^^^^^^^^^^^^^`
Mark `unsafe_pin_internals` as `incomplete`. This thus still makes it technically possible to enable the feature, and thus to trigger UB without `unsafe`, but this is fine since incomplete features are known to be potentially unsound (labelled "may not be safe"). This follows from the discussion at https://github.com/rust-lang/rust/pull/93176#discussion_r799413561 2022-01-23 18:34:46 -06:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Mark `unsafe_pin_internals` as `incomplete`. This thus still makes it technically possible to enable the feature, and thus to trigger UB without `unsafe`, but this is fine since incomplete features are known to be potentially unsound (labelled "may not be safe"). This follows from the discussion at https://github.com/rust-lang/rust/pull/93176#discussion_r799413561 2022-01-23 18:34:46 -06:00