Issue 4940 - ICE(symbol.c): Accessing tuple-typed field of struct literal with user-defined constructor #609
Conversation
This file contains 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
From: te->exps is ((DeclarationExp __tup = einit, __tup.var_0), __tup.var_1, ..., __tup.var_n) . To: te->exps is ((DeclarationExp __tup = einit, __tup).var_0, __tup.var_1, ..., __tup.var_n) . Now can extract einit with ((DotVarExp *)(*te->exps)[0])->isTemp(). On compile-time tuple access in IndexExp, restore einit to keep side-effect.
…eral with user-defined constructor
WalterBright
added a commit
that referenced
this pull request
Jan 17, 2012
Issue 4940 - ICE(symbol.c): Accessing tuple-typed field of struct literal with user-defined constructor
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.
http://d.puremagic.com/issues/show_bug.cgi?id=4940
Explanation of bug mechanism:
http://d.puremagic.com/issues/show_bug.cgi?id=4940#c3
e1.tupleofshould be translated by the same way inDotVarExp::semantic()to save side effect ofe1.2012/01/10
Issue 7263 - Tuple slicing + -O switch causes "used before set" error
Tuple slicing has same problem.