-
-
Notifications
You must be signed in to change notification settings - Fork 609
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
fix Issue 17423 - pointer assignment to in member function is not ac… #7999
Conversation
|
Thanks for your pull request, @WalterBright! Bugzilla references
|
09bdcbd to
2cdcaa3
Compare
| foreach (VarDeclaration v; ad.fields) | ||
| { | ||
| if (v.hasPointers()) | ||
| return stc; |
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.
This looks suspicious.
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.
don't know what you mean
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.
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 it? Please don't make me guess.
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.
Sorry - my point was only that these two lines are uncovered, thus return stc is never called and thus all code that you added has never an effect for the testcase.
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.
never mind, I see
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.
Should be covered now.
| foreach(_; o) { i = 0; } | ||
| i = x; | ||
| } | ||
| } |
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.
The test file from the bug report still triggers in a segfault (with this PR).
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.
It fails to compile with -dip1000
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.
Oh my point was that 17423 isn't fixed by this PR because the segfault still exists and with -dip1000 it currently doesn't segfault: https://run.dlang.io/is/W1DGlg
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.
My point is -dip1000 is required to fix it. The whole point of dip1000 is to fix these sorts of issues.
|
Why are the coverage test results not showing up in the code view anymore? |
|
Yes, it worked for me too after I hit refresh. Thanks for the tip! Anyhow, it's all green now and good to go. |
|
FYI: I opened an issue (codecov/browser-extension#53), but the extension seems to be unmaintained (codecov/browser-extension#52). |
|
Done. Please consider returning the favor by reviewing some of the pull requests that require someone with your unique skills and position. |


…counted for