rename GCA features - #163306
rename GCA features#163306
Conversation
|
HIR ty lowering was modified cc @fmease Some changes occurred in cc @BoxyUwU The rustc-dev-guide subtree was changed. If your future PRs only touch the subtree, consider submitting them directly to rust-lang/rustc-dev-guide, which is where the document is primarily maintained (and has faster CI).
cc @rust-lang/rust-analyzer This PR changes a file inside changes to the core type system cc @lcnr
cc @rust-lang/rustfmt Some changes occurred in match checking cc @Nadrieril Some changes occurred in compiler/rustc_attr_parsing cc @jdonszelmann, @JonathanBrouwer The parser was modified, potentially altering the grammar of (stable) Rust cc @fmease
cc @rust-lang/clippy |
|
|
10d08aa to
eef103d
Compare
|
@bors r+ p=1 |
|
ah wait @bors r- can you add the renamed features to removed.rs |
|
This pull request was unapproved. |
|
r=me after above :> |
eef103d to
88f1088
Compare
|
@bors r=BoxyUwU p=1 trying out the fancy new "approve when ci passes" functionality~ |
|
⌛ Commit 88f1088 has been tentatively approved by |
This comment has been minimized.
This comment has been minimized.
What is this?This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.Comparing ecd8f1d (parent) -> 5ceaf66 (this PR) Test differencesShow 55 test diffsStage 1
Stage 2
Additionally, 4 doctest diffs were found. These are ignored, as they are noisy. Job group index
Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard 5ceaf6608eb354c2f5bbb3b8d974caa367dac81c --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (5ceaf66): comparison URL. Overall result: ❌✅ regressions and improvements - please read:Our benchmarks found a performance regression caused by this PR. Next Steps:
@rustbot label: +perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 1.3%, secondary 1.8%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary -2.7%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis perf run didn't have relevant results for this metric. Bootstrap: 490.913s -> 488.629s (-0.47%) |
Nightly renamed them in rust-lang/rust#163306: generic_const_args -> gca_const_items, min_generic_const_args -> gca_min_const_items, macroless_generic_const_args -> gca_macroless_args. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fixes rust-lang/project-const-generics#114
We would like to publish posts soon that GCE is dying and GCA is the future. As part of that, we want the feature gates/etc. to be in their final-ish shape. We discussed a lot of naming bikesheds in the zulip thread #project-const-generics > talkies at last @ 💬, namely:
min_generic_const_args->gca_min_const_itemsgeneric_const_args->gca_const_itemsmacroless_generic_const_args->gca_macroless_argsmacroless_const_item_generic_const_args->gca_macroless_itemsthings that were discussed in that Zulip thread, but are not part of this PR:
gca_adtsand/orgca_arrays(the feature is not created yet)DirectConstArgContextenum is in a vaguely awkwardly named spot after this PR. I intend to clean it up as part of creating thegca_adtsfeature (perhaps turning it into a bitflags for allowed syntax, or something)direct_const_arg!macro togca!- this was done in rename direct_const_arg! to gca! #163198type const, introducing#[always_gca]- this was done in yeettype const#162517r? @BoxyUwU