Skip to content

C++: fix FP with ExprHasNoEffect in defaulted func#1498

Merged
jbj merged 1 commit intogithub:masterfrom
rdmarsh2:rdmarsh/exprHasNoEffect-defaulted-functions
Jun 27, 2019
Merged

C++: fix FP with ExprHasNoEffect in defaulted func#1498
jbj merged 1 commit intogithub:masterfrom
rdmarsh2:rdmarsh/exprHasNoEffect-defaulted-functions

Conversation

@rdmarsh2
Copy link
Contributor

This is a workaround for an extractor issue where expressions in a
defaulted function are not always marked as generated. I haven't yet been
able to reproduce the issue in a test case.

@rdmarsh2 rdmarsh2 added the C++ label Jun 25, 2019
@rdmarsh2 rdmarsh2 requested a review from a team as a code owner June 25, 2019 22:32
@jbj
Copy link
Contributor

jbj commented Jun 26, 2019

Tests failed.

Is there a project on lgtm.com or a forum post that motivates this PR?

This is a workaround for an extractor issue where expressions in a
defaulted function are not always marked as generated. I haven't yet been
able to reproduce the issue in a test case.
@rdmarsh2 rdmarsh2 force-pushed the rdmarsh/exprHasNoEffect-defaulted-functions branch from 0eb706d to 8994a5a Compare June 26, 2019 16:11
@rdmarsh2
Copy link
Contributor Author

Fixed the test failure. This should fix the FPs reported here.

@jbj jbj merged commit c29ef90 into github:master Jun 27, 2019
@rdmarsh2 rdmarsh2 deleted the rdmarsh/exprHasNoEffect-defaulted-functions branch July 11, 2019 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments