-
Notifications
You must be signed in to change notification settings - Fork 14k
MGCA: Syntactically distinguish anon const const args #149136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
BoxyUwU
wants to merge
1
commit into
rust-lang:main
Choose a base branch
from
BoxyUwU:mgca_explicit_anon_consts
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+788
−310
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
Some changes occurred in compiler/rustc_builtin_macros/src/autodiff.rs cc @ZuseZ4 |
Collaborator
|
|
Collaborator
|
The job Click to see the possible cause of the failure (guessed by this bot) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
S-waiting-on-review
Status: Awaiting review from the assignee but also interested parties.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
T-rustdoc
Relevant to the rustdoc 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.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
r? oli-obk
tracking issue: #132980
Syntactically distinguishing anon consts
Implementation wise the first thing this PR does is require that anon const const args are syntactically distinguishable from other kinds of args under mgca. We now use
const { ... }in const argument position to denote an anon const:This restriction is only placed when mgca is enabled. There should be no effect on stable.
This restriction allows us to create
DefIds for anon consts only when actually required. When it is syntactically ambiguous whether a const argument is an anon const or not we are forced to conservatively create aDefIdfor every const argument even if it doesn't wind up needing one.This works fine on stable but under
mgcawe can wind up with anon consts nested inside non-anon-const const arguments resulting in a brokenDefIdtree. See #148838 where an anon const arg inside of a path arg winds up with a parent of a conservatively createdDefIdthat doesn't actually correspond to an anon const, resulting in an ICE.With #149114 every field initialiser in a const argument would become a place where there could possibly be an anon const. This would also get worse once we support tuple constructors- now every function argument is a place where there could possibly be an anon const.
We introduce this restriction to avoid creating massive amounts of unused
DefIds that make the parent tree significantly more complicated, and to avoid having to paper over this issue in things likegenerics_of.Fixes #148838
It also must be syntactically clear from context whether
'_means an inference lifetime or an elided lifetime parameter. This restriction will allow us to properly resolve'_in const arguments in mgca. This PR doesn't actually fix handle this, but we could do so trivially after this lands.