about summary refs log tree commit diff
path: root/compiler/rustc_feature/src/removed.rs
AgeCommit message (Collapse)AuthorLines
2023-03-12Remove `box_syntax` from AST and use in toolsclubby789-0/+2
2023-02-28Remove the `capture_disjoint_fields` featureclubby789-0/+2
2022-09-26replace stabilization placeholdersPietro Albini-1/+1
2022-08-28Remove `register_attr` featureYuki Okushi-0/+3
Signed-off-by: Yuki Okushi <jtitor@2k36.org>
2022-07-13add array tests, cleanup, tidy, and blessRalf Jung-1/+1
2022-07-13remove untagged_union feature gateRalf Jung-0/+3
2022-06-13Rollup merge of #97875 - JohnTitor:rm-infer-static-outlives-requirements, ↵Matthias Krüger-0/+3
r=pnkfelix Remove the `infer_static_outlives_requirements` feature Closes #54185 r? ``@pnkfelix``
2022-06-09Stabilize the `bundle` native library modifierVadim Petrochenkov-0/+3
2022-06-08Remove the `infer_static_outlives_requirements` featureYuki Okushi-0/+3
2022-05-21Remove feature: `crate` visibility modifierJacob Pratt-0/+2
2022-02-24Remove in-band lifetimesMichael Goulet-0/+3
2022-01-28remove allow_fail test flagyuhaixin.hx-0/+2
2021-11-24Create rustdoc_internals feature gateGuillaume Gomez-0/+6
2021-11-15Alphabetize language featuresJacob Pratt-96/+94
This should significantly reduce the frequency of merge conflicts.
2021-09-09Ignore automatically derived impls of `Clone` and `Debug` in dead code analysisFabian Wolff-2/+0
2021-09-07Fix typo in `const_generics` replaced with `adt_const_params` noteMingwei Samuel-1/+1
2021-08-30`feature(const_param_types)` -> `feature(adt_const_params)`lcnr-1/+1
2021-08-30`feature(const_generics)` -> `feature(const_param_types)`lcnr-0/+3
2021-08-30rename const_evaluatable_checked to generic_const_exprsEllen-0/+4
:sparkles:
2021-08-27Introduce `~const`Deadbeef-0/+3
- [x] Removed `?const` and change uses of `?const` - [x] Added `~const` to the AST. It is gated behind const_trait_impl. - [x] Validate `~const` in ast_validation. - [ ] Add enum `BoundConstness` to the HIR. (With variants `NotConst` and `ConstIfConst` allowing future extensions) - [ ] Adjust trait selection and pre-existing code to use `BoundConstness`. - [ ] Optional steps (*for this PR, obviously*) - [ ] Fix #88155 - [ ] Do something with constness bounds in chalk
2021-08-10Replace #[plugin_registrar] with exporting __rustc_plugin_registrarbjorn3-1/+4
2021-08-03rustc: Fill out remaining parts of C-unwind ABIAlex Crichton-0/+5
This commit intends to fill out some of the remaining pieces of the C-unwind ABI. This has a number of other changes with it though to move this design space forward a bit. Notably contained within here is: * On `panic=unwind`, the `extern "C"` ABI is now considered as "may unwind". This fixes a longstanding soundness issue where if you `panic!()` in an `extern "C"` function defined in Rust that's actually UB because the LLVM representation for the function has the `nounwind` attribute, but then you unwind. * Whether or not a function unwinds now mainly considers the ABI of the function instead of first checking the panic strategy. This fixes a miscompile of `extern "C-unwind"` with `panic=abort` because that ABI can still unwind. * The aborting stub for non-unwinding ABIs with `panic=unwind` has been reimplemented. Previously this was done as a small tweak during MIR generation, but this has been moved to a separate and dedicated MIR pass. This new pass will, for appropriate functions and function calls, insert a `cleanup` landing pad for any function call that may unwind within a function that is itself not allowed to unwind. Note that this subtly changes some behavior from before where previously on an unwind which was caught-to-abort it would run active destructors in the function, and now it simply immediately aborts the process. * The `#[unwind]` attribute has been removed and all users in tests and such are now using `C-unwind` and `#![feature(c_unwind)]`. I think this is largely the last piece of the RFC to implement. Unfortunately I believe this is still not stabilizable as-is because activating the feature gate changes the behavior of the existing `extern "C"` ABI in a way that has no replacement. My thinking for how to enable this is that we add support for the `C-unwind` ABI on stable Rust first, and then after it hits stable we change the behavior of the `C` ABI. That way anyone straddling stable/beta/nightly can switch to `C-unwind` safely.
2021-07-28min_type_alias_impl_trait is going to be removed in 1.56Santiago Pastorino-1/+1
2021-07-27Remove min_type_alias_impl_trait featureSantiago Pastorino-0/+4
2021-07-27existential_type was removed in favor of type_alias_impl_traitSantiago Pastorino-1/+1
2021-07-19Improve impl_trait_in_bindings removed feature textSantiago Pastorino-1/+1
2021-07-18Remove impl_trait_in_bindings feature flagSantiago Pastorino-0/+4
2021-07-10remove const_raw_ptr_to_usize_cast featureRalf Jung-0/+4
2021-06-04Remove `doc(include)`Joshua Nelson-0/+4
2021-05-09remove const_fn feature gateRalf Jung-0/+3
2021-04-23Add pub_macro_rules to the list of removed featuresSantiago Pastorino-0/+2
2021-04-16Remove #[main] attribute.Charles Lew-0/+2
2021-04-03Remove attribute `#[link_args]`Vadim Petrochenkov-0/+4
2021-04-02Auto merge of #80965 - camelid:rename-doc-spotlight, r=jyn514bors-0/+5
Rename `#[doc(spotlight)]` to `#[doc(notable_trait)]` Fixes #80936. "spotlight" is not a very specific or self-explaining name. Additionally, the dialog that it triggers is called "Notable traits". So, "notable trait" is a better name. * Rename `#[doc(spotlight)]` to `#[doc(notable_trait)]` * Rename `#![feature(doc_spotlight)]` to `#![feature(doc_notable_trait)]` * Update documentation * Improve documentation r? `@Manishearth`
2021-03-15Rename `#[doc(spotlight)]` to `#[doc(notable_trait)]`Camelid-0/+5
"spotlight" is not a very specific or self-explaining name. Additionally, the dialog that it triggers is called "Notable traits". So, "notable trait" is a better name. * Rename `#[doc(spotlight)]` to `#[doc(notable_trait)]` * Rename `#![feature(doc_spotlight)]` to `#![feature(doc_notable_trait)]` * Update documentation * Improve documentation
2021-03-15Replace `type_alias_impl_trait` by `min_type_alias_impl_trait` with no ↵Oli Scherer-1/+1
actual changes in behaviour This makes `type_alias_impl_trait` not actually do anything anymore
2021-01-30Remove const_in_array_rep_exprkadmin-0/+3
2020-11-23Rename `optin_builtin_traits` to `auto_traits`Camelid-1/+4
They were originally called "opt-in, built-in traits" (OIBITs), but people realized that the name was too confusing and a mouthful, and so they were renamed to just "auto traits". The feature flag's name wasn't updated, though, so that's what this PR does. There are some other spots in the compiler that still refer to OIBITs, but I don't think changing those now is worth it since they are internal and not particularly relevant to this PR. Also see <https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/opt-in.2C.20built-in.20traits.20(auto.20traits).20feature.20name>.
2020-09-17Fix 'FIXME' about using NonZeroU32 instead of u32.Mara Bos-3/+3
It was blocked by #58732 (const fn NonZeroU32::new), which is fixed now.
2020-08-30mv compiler to compiler/mark-0/+129
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-26 14:29:39 +0000