We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think that the "uses" block should never be marked as a duplicate. It often happens that two units have the same this block and it is not a mistake.
The text was updated successfully, but these errors were encountered:
I see your point we somehow never realised this. I'm gonna think about a easier solution. But since this feature has its uses we'll keep it.
Sorry, something went wrong.
Slightlty decreased priority of ConstructorWithoutInheritedStatementR…
65b2325
…ule and DestructorWithoutInheritedStatementRule as there are many false positives. See issue SandroLuck#3
No branches or pull requests
I think that the "uses" block should never be marked as a duplicate.
It often happens that two units have the same this block and it is not a mistake.
The text was updated successfully, but these errors were encountered: