Feature gate #[static_assert].
The API this exposes is a little strange (being attached to `static`s), so it makes sense to conservatively feature gate it. If it is highly popular, it is possible to reverse this gating.
This commit is contained in:
parent
1576142495
commit
c195783c05
9 changed files with 36 additions and 13 deletions
|
|
@ -2495,6 +2495,12 @@ The currently implemented features of the reference compiler are:
|
|||
|
||||
* `staged_api` - Allows usage of stability markers and `#![staged_api]` in a crate
|
||||
|
||||
* `static_assert` - The `#[static_assert]` functionality is experimental and
|
||||
unstable. The attribute can be attached to a `static` of
|
||||
type `bool` and the compiler will error if the `bool` is
|
||||
`false` at compile time. This version of this functionality
|
||||
is unintuitive and suboptimal.
|
||||
|
||||
* `start` - Allows use of the `#[start]` attribute, which changes the entry point
|
||||
into a Rust program. This capabiilty, especially the signature for the
|
||||
annotated function, is subject to change.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue