[WIP] Structural inititalization#143625
Draft
beepster4096 wants to merge 6 commits intorust-lang:mainfrom
Draft
Conversation
This comment has been minimized.
This comment has been minimized.
changes are seperate so git will recognize as a move
05eb8e2 to
f328f70
Compare
This comment has been minimized.
This comment has been minimized.
with incorrect error output though
f328f70 to
0e01218
Compare
This comment has been minimized.
This comment has been minimized.
b78cbf5 to
b056ed0
Compare
Collaborator
|
☔ The latest upstream changes (presumably #144488) made this pull request unmergeable. Please resolve the merge conflicts. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds the
structural_initfeature, allowing structs and tuples to be initialized field by field.This is typically called "partial initialization" but I have named this process "structural initialization" as I feel that "partial" does not make sense when you are initializing the entire struct this way. Obviously bikeshedable, since I just came up with this on my own without any consensus.
These are the semantics I have implemented:
These semantics have the strange effect that
struct Empty;and()are always considered initialized. Its trivial to disable this, it just needs a decision at some point.WIP:
ui\nll\issue-21232-**tests already exist and should be modifiedcc #54987