-
-
Notifications
You must be signed in to change notification settings - Fork 755
Fix Issue 23182 - Can't assign struct with opAssign to SumType in CTFE #8474
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about also adding a CTFE-version of
movebeing executable at compile-time by replacing thememcpywith anvoid[]-copyfor the__ctfe-case? Ping, @RazvanN7.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doing a proper
movein CTFE is impossible, because CTFE does not support reinterpreting casts (which includes casting tovoid[]). See PR #936 for related discussion. The best that can be done is to fall back to a copy, as is done here.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Afaict, the core of this limitation is rather that the compiler is lacking the ability to automatically (internally) perform a move of
valueintothisatthis = value;as this statment is the last statement that references
valuebeforethisis returned. The are more such cornercases where the compiler should move (but currently doesn't) thereby avoiding thesestatic if-branchings onisCopyable!T. Afaict, if the compiler had that ability that would unlock being able to use non-copyable types at CTFE at least in situations like these. Ping, @andralex @RazvanN7 @WalterBright.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, if the compiler could automatically turn these last-use assignments into moves, the explicit calls to
moveandforwardwould no longer be necessary in the first place, so there would be no need to add workarounds to avoid calling them in CTFE.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed. That would be awesome. Moreover, there are many Phobos' ranges that would be able to operate on non-copyable source range types if that restriction was lifted.