make rustc_allow_const_fn_unstable an actual rustc_attrs attribute#152749
make rustc_allow_const_fn_unstable an actual rustc_attrs attribute#152749rust-bors[bot] merged 1 commit intorust-lang:mainfrom
rustc_allow_const_fn_unstable an actual rustc_attrs attribute#152749Conversation
|
cc @rust-lang/wg-const-eval |
|
r? @mati865 rustbot has assigned @mati865. Use Why was this reviewer chosen?The reviewer was selected based on:
|
This comment has been minimized.
This comment has been minimized.
68ff184 to
e335f96
Compare
| Some("removed in favor of `#![register_tool]`"), 66070), | ||
| (removed, rust_2018_preview, "1.76.0", None, | ||
| Some("2018 Edition preview is no longer relevant")), | ||
| (removed, rustc_allow_const_fn_unstable, "CURRENT_RUSTC_VERSION", Some(69399), Some("merged into `#![feature(rustc_attrs)]`")), |
There was a problem hiding this comment.
I wonder if there's actual merit in keeping track of removed internal features 🤔. After all, in theory nobody other than stdlib authors should've used and should use this attribute. Context: I'm always eager to get rid of unnecessary baggage.
(#69399 isn't even a proper tracking issue ^^).
There was a problem hiding this comment.
agree with fmease here
There was a problem hiding this comment.
Removed it.
That said, I was told to do the opposite in #152746 (comment) earlier today.
There was a problem hiding this comment.
Thanks for bringing this up. As a general rule, we indeed want to keep track of removed features, so users have an easier time migrating. Of course, there are probably gray areas where the opinion of reviewers might diverge.
In the case of the now removed 5723 feature, I don't know if it was truly necessary to keep books, I haven't looked into it. It depends on the ecosystem impact I feel like. Still, keeping record is the safe & generally desired default.
Specifically in the case of the specially flagged internal features however (which are only a thing since 2 years ago maybe?) I'm set on 'purging the archives' since I don't care about providing hypothetical users who aren't stdlib devs further internal information for migrating a feature they shouldn't've used in the first place. rustc carries enough historical baggage, I don't want to increase it.
|
r? me |
|
I think this one should just be properly removed |
|
@rustbot author |
|
Reminder, once the PR becomes ready for a review, use |
e335f96 to
83ef505
Compare
|
I think this is genuinely nicest, and it's internal anyway. If someone cares enough, undo that decision, but it's an @bors r+ rollup from me |
…zelmann make `rustc_allow_const_fn_unstable` an actual `rustc_attrs` attribute It is already named like one, but used to have its own feature gate, which this PR now removes in favor of just using `#![feature(rustc_attrs)]`. Most of the diff is just the line number changes in `malformed-attrs.stderr`.
…zelmann make `rustc_allow_const_fn_unstable` an actual `rustc_attrs` attribute It is already named like one, but used to have its own feature gate, which this PR now removes in favor of just using `#![feature(rustc_attrs)]`. Most of the diff is just the line number changes in `malformed-attrs.stderr`.
…zelmann make `rustc_allow_const_fn_unstable` an actual `rustc_attrs` attribute It is already named like one, but used to have its own feature gate, which this PR now removes in favor of just using `#![feature(rustc_attrs)]`. Most of the diff is just the line number changes in `malformed-attrs.stderr`.
Rollup of 19 pull requests Successful merges: - #145399 (Unify wording of resolve error) - #150473 (tail calls: fix copying non-scalar arguments to callee) - #152637 (Add a note about elided lifetime) - #152657 (std: move `exit` out of PAL) - #152729 (compiler: Don't mark `SingleUseConsts` MIR pass as "required for soundness") - #152753 (remove the explicit error for old `rental` versions) - #152758 (Remove ShallowInitBox.) - #151530 (Fix invalid `mut T` suggestion for `&mut T` in missing lifetime error) - #152179 (Add documentation note about signed overflow direction) - #152474 (Implement opt-bisect-limit for MIR) - #152509 (tests/ui/test-attrs: add annotations for reference rules) - #152672 (std: use libc version of `_NSGetArgc`/`_NSGetArgv`) - #152711 (resolve: Disable an assert that no longer holds) - #152732 (add regression test for 147958) - #152745 (Fix ICE in `suggest_param_env_shadowing` with incompatible args) - #152749 (make `rustc_allow_const_fn_unstable` an actual `rustc_attrs` attribute) - #152756 (Miri: recursive validity: also recurse into Boxes) - #152770 (carryless_mul: mention the base) - #152778 (Update tracking issue number for final_associated_functions)
Rollup of 20 pull requests Successful merges: - #145399 (Unify wording of resolve error) - #150473 (tail calls: fix copying non-scalar arguments to callee) - #152637 (Add a note about elided lifetime) - #152729 (compiler: Don't mark `SingleUseConsts` MIR pass as "required for soundness") - #152751 (Rename dep node "fingerprints" to distinguish key and value hashes) - #152753 (remove the explicit error for old `rental` versions) - #152758 (Remove ShallowInitBox.) - #151530 (Fix invalid `mut T` suggestion for `&mut T` in missing lifetime error) - #152179 (Add documentation note about signed overflow direction) - #152474 (Implement opt-bisect-limit for MIR) - #152509 (tests/ui/test-attrs: add annotations for reference rules) - #152672 (std: use libc version of `_NSGetArgc`/`_NSGetArgv`) - #152711 (resolve: Disable an assert that no longer holds) - #152725 (Rework explanation of CLI lint level flags) - #152732 (add regression test for 147958) - #152745 (Fix ICE in `suggest_param_env_shadowing` with incompatible args) - #152749 (make `rustc_allow_const_fn_unstable` an actual `rustc_attrs` attribute) - #152756 (Miri: recursive validity: also recurse into Boxes) - #152770 (carryless_mul: mention the base) - #152778 (Update tracking issue number for final_associated_functions)
Rollup merge of #152749 - cyrgani:rustc-allow-const, r=jdonszelmann make `rustc_allow_const_fn_unstable` an actual `rustc_attrs` attribute It is already named like one, but used to have its own feature gate, which this PR now removes in favor of just using `#![feature(rustc_attrs)]`. Most of the diff is just the line number changes in `malformed-attrs.stderr`.
It is already named like one, but used to have its own feature gate, which this PR now removes in favor of just using
#![feature(rustc_attrs)].Most of the diff is just the line number changes in
malformed-attrs.stderr.