Skip to content

Conversation

@jbj
Copy link
Contributor

@jbj jbj commented Nov 20, 2018

This rule, named "No virtual destructor", was supposed to be superseded by cpp/virtual-destructor in #408, but that PR didn't actually disable this rule, so both rules are now active in the LGTM suite.

This PR disables the rule by removing @precision. We're still discussing the best way to disable rules that are precise and valid but not universally applicable. For now, removing @precision is consistent with how we're keeping most other JSF queries from appearing on LGTM.

This rule, named "No virtual destructor", was supposed to be superseded
by `cpp/virtual-destructor` in 0c796de, but that commit didn't
actually disable this rule, so both rules are now active in the LGTM
suite.

This commit disables the rule by removing `@precision`. We're still
discussing the best way to disable rules that are precise and valid but
not universally applicable. For now, removing `@precision` is consistent
with how we're keeping most other JSF queries from appearing on LGTM.
@jbj jbj added the C++ label Nov 20, 2018
@jbj jbj requested a review from a team as a code owner November 20, 2018 08:50
Copy link
Contributor

@geoffw0 geoffw0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest turning it down to warning medium, as it looks to be slightly less accurate than the other version of the query - but that would not be enough to disable it on LGTM.

@geoffw0 geoffw0 modified the milestone: 1.19 Nov 20, 2018
@geoffw0 geoffw0 merged commit 0493b68 into github:master Nov 20, 2018
cklin pushed a commit that referenced this pull request May 23, 2022
Fix performance issue with 'package'
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.

3 participants