rust/compiler/rustc_feature/src/accepted.rs, branch 1.77.2

Bump version placeholders

2024-02-03T21:37:58+00:00

Revert "Auto merge of #118133 - Urgau:stabilize_trait_upcasting, r=WaffleLapkin"

2024-01-22T14:24:31+00:00

This reverts commit 6d2b84b3ed7848fd91b8d6151d4451b3103ed816, reversing changes made to 73bc12199ea8c7651ed98b069c0dd6b0bb5fabcf.

Set `c_str_literals` stabilization version back to `CURRENT_RUSTC_VERSION`

2024-01-11T19:46:02+00:00

`c_str_literals`'s stabilization has been delayed to 1.77 (https://github.com/rust-lang/rust/pull/119528).

update version placeholders

2023-12-22T10:01:42+00:00

Remove edition umbrella features.

2023-12-10T21:03:28+00:00

Auto merge of #117472 - jmillikin:stable-c-str-literals, r=Nilstrieb

2023-12-01T13:33:55+00:00

Stabilize C string literals RFC: https://rust-lang.github.io/rfcs/3348-c-str-literal.html Tracking issue: https://github.com/rust-lang/rust/issues/105723 Documentation PR (reference manual): https://github.com/rust-lang/reference/pull/1423 # Stabilization report Stabilizes C string and raw C string literals (`c"..."` and `cr#"..."#`), which are expressions of type [`&CStr`](https://doc.rust-lang.org/stable/core/ffi/struct.CStr.html). Both new literals require Rust edition 2021 or later. ```rust const HELLO: &core::ffi::CStr = c"Hello, world!"; ``` C strings may contain any byte other than `NUL` (`b'\x00'`), and their in-memory representation is guaranteed to end with `NUL`. ## Implementation Originally implemented by PR https://github.com/rust-lang/rust/pull/108801, which was reverted due to unintentional changes to lexer behavior in Rust editions < 2021. The current implementation landed in PR https://github.com/rust-lang/rust/pull/113476, which restricts C string literals to Rust edition >= 2021. ## Resolutions to open questions from the RFC * Adding C character literals (`c'.'`) of type `c_char` is not part of this feature. * Support for `c"..."` literals does not prevent `c'.'` literals from being added in the future. * C string literals should not be blocked on making `&CStr` a thin pointer. * It's possible to declare constant expressions of type `&'static CStr` in stable Rust (as of v1.59), so C string literals are not adding additional coupling on the internal representation of `CStr`. * The unstable `concat_bytes!` macro should not accept `c"..."` literals. * C strings have two equally valid `&[u8]` representations (with or without terminal `NUL`), so allowing them to be used in `concat_bytes!` would be ambiguous. * Adding a type to represent C strings containing valid UTF-8 is not part of this feature. * Support for a hypothetical `&Utf8CStr` may be explored in the future, should such a type be added to Rust.

Stabilize RFC3324 dyn upcasting coercion

2023-11-22T12:56:36+00:00

Aka trait_upcasting feature. And also adjust the `deref_into_dyn_supertrait` lint.

Substitute version placeholders

2023-11-16T00:40:51+00:00

Stabilize C string literals

2023-11-01T00:16:34+00:00

Rename `ACTIVE_FEATURES` as `UNSTABLE_FEATURES`.

2023-10-15T21:17:23+00:00

It's a better name, and lets "active features" refer to the features that are active in a particular program, due to being declared or enabled by the edition. The commit also renames `Features::enabled` as `Features::active` to match this; I changed my mind and have decided that "active" is a little better thatn "enabled" for this, particularly because a number of pre-existing comments use "active" in this way. Finally, the commit renames `Status::Stable` as `Status::Accepted`, to match `ACCEPTED_FEATURES`.