Skip to content

implement #![feature(macroless_generic_const_args)] - #159058

Merged
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
khyperia:macroless_generic_const_args
Jul 21, 2026
Merged

implement #![feature(macroless_generic_const_args)]#159058
rust-bors[bot] merged 1 commit into
rust-lang:mainfrom
khyperia:macroless_generic_const_args

Conversation

@khyperia

@khyperia khyperia commented Jul 10, 2026

Copy link
Copy Markdown
Member

tracking issue: #159006

lots of description of what is happening here in the tracking issue, not gonna copypaste it into here :)

the test situation is that after discussion with boxy of whether our mgca tests should be:

  • keep them under only min_generic_const_args, and add direct_const_arg!() where it's needed
  • keep the code contents as-is, and add #![feature(macroless_generic_const_args)] where it's needed

the second seems more desirable, so that's what I did. There are still quite a few tests that only have min_generic_const_args without macroless_generic_const_args (140 of them, to be exact - rg --files-without-match macroless_generic_const_args $(rg -g '*.rs' --files-with-matches min_generic_const_args tests) | wc -l, and now 90 with macroless_generic_const_args)

r? @BoxyUwU

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

PG-exploit-mitigations Project group: Exploit mitigations S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants