rust/tests/rustdoc/issue-18199.rs

// compile-flags:--test

#![doc(test(attr(feature(staged_api))))]

/// ```
/// #![allow(internal_features)]
/// #![unstable(feature="test", issue="18199")]
/// fn main() {}
/// ```
pub fn foo() {}
rustdoc: Allowing specifying attrs for doctests This adds support in rustdoc to blanket apply crate attributes to all doc tests for a crate at once. The syntax for doing this is: #![doc(test(attr(...)))] Each meta item in `...` will be applied to each doctest as a crate attribute. cc #18199 2015-04-07 01:39:39 +00:00			`// compile-flags:--test`

			`#![doc(test(attr(feature(staged_api))))]`

			/// ```
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 20:54:53 +00:00			`/// #![allow(internal_features)]`
Add missing annotations and some tests 2015-11-16 16:54:28 +00:00			`/// #![unstable(feature="test", issue="18199")]`
rustdoc: Allowing specifying attrs for doctests This adds support in rustdoc to blanket apply crate attributes to all doc tests for a crate at once. The syntax for doing this is: #![doc(test(attr(...)))] Each meta item in `...` will be applied to each doctest as a crate attribute. cc #18199 2015-04-07 01:39:39 +00:00			`/// fn main() {}`
			/// ```
			`pub fn foo() {}`