Skip to content
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

More conservative fix for issue 12900 - Wrong code in IfStatement condition Expression #3685

Merged
merged 1 commit into from
Jun 25, 2014

Conversation

9rnsr
Copy link
Contributor

@9rnsr 9rnsr commented Jun 21, 2014

Improvement for the PR #3662.

  1. Using t1->implicitConvTo(t2) >= MATCHconst has a known problem (eg. issue 5363).
  2. Both conversions *&ex to ex and &*ex to ex should be handled in same way.

@WalterBright
Copy link
Member

Kenji, thanks for finding a better way. Can you add the test case here?

@9rnsr
Copy link
Contributor Author

9rnsr commented Jun 25, 2014

Added a bit complex assert in DotVarExp::toElem.

WalterBright added a commit that referenced this pull request Jun 25, 2014
More conservative fix for issue 12900 - Wrong code in IfStatement condition Expression
@WalterBright WalterBright merged commit d664dae into dlang:master Jun 25, 2014
@9rnsr 9rnsr deleted the fix12900 branch June 26, 2014 04:09
Trass3r added a commit to Trass3r/ldc that referenced this pull request Jun 29, 2014
redstar added a commit to ldc-developers/ldc that referenced this pull request Jun 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants