Separate contract feature gates for the internal machinery
The extended syntax for function signature that includes contract clauses should never be user exposed versus the interface we want to ship externally eventually.
This commit is contained in:
parent
b279ff9dcf
commit
6a6c6b891b
20 changed files with 210 additions and 28 deletions
|
@ -608,6 +608,10 @@ declare_features! (
|
|||
(unstable, return_type_notation, "1.70.0", Some(109417)),
|
||||
/// Allows `extern "rust-cold"`.
|
||||
(unstable, rust_cold_cc, "1.63.0", Some(97544)),
|
||||
/// Allows use of contracts attributes.
|
||||
(unstable, rustc_contracts, "CURRENT_RUSTC_VERSION", Some(133866)),
|
||||
/// Allows access to internal machinery used to implement contracts.
|
||||
(unstable, rustc_contracts_internals, "CURRENT_RUSTC_VERSION", Some(133866)),
|
||||
/// Allows use of x86 SHA512, SM3 and SM4 target-features and intrinsics
|
||||
(unstable, sha512_sm_x86, "1.82.0", Some(126624)),
|
||||
/// Allows the use of SIMD types in functions declared in `extern` blocks.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue