https://bugs.kde.org/show_bug.cgi?id=363540
Bug ID: 363540
Summary: detaching-member false positive if non-const reference
is stored
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=359000
--- Comment #3 from Nyall Dawson ---
Here's a simple test case:
#include
#include
int main(int, char **)
{
QString string; //no warning
QList list; //no warning
QVariant var; //no warning
QIcon i; //no warning
int num; //warning
https://bugs.kde.org/show_bug.cgi?id=359305
Nyall Dawson changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=359306
Bug ID: 359306
Summary: new check idea: avoid using Q_FOREACH to iterate over
QMap/QHash keys and retrieve values inside loop
Product: clazy
Version: unspecified
Platform: Other
https://bugs.kde.org/show_bug.cgi?id=359305
Bug ID: 359305
Summary: false positives in container-anti-pattern
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: nor
https://bugs.kde.org/show_bug.cgi?id=359000
Bug ID: 359000
Summary: new check: warn about unused Qt objects
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: norma
https://bugs.kde.org/show_bug.cgi?id=358519
--- Comment #4 from Nyall Dawson ---
I wonder if allowing any const calls might work too. This would allow
destructors with debugging and other non dangerous code.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=358519
--- Comment #2 from Nyall Dawson ---
I'm honestly not sure if there's any good reason for them, but the codebase I'm
working on is littered with them.
Of course, if feel free to close this if you also think there's absolutely no
good reason why an emp
https://bugs.kde.org/show_bug.cgi?id=358519
Bug ID: 358519
Summary: rule-of-three: ignore trivial destructors
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: nor
https://bugs.kde.org/show_bug.cgi?id=356755
Bug ID: 356755
Summary: detaching-member: don't warn when begin()/end() used
in qSort
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
Sta
https://bugs.kde.org/show_bug.cgi?id=356699
--- Comment #6 from Nyall Dawson ---
...And I also just realised my example was very poorly chosen ;)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356699
--- Comment #5 from Nyall Dawson ---
Yes - that's what I was referring to (values). Sorry, should have made that
clearer to begin with!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356699
--- Comment #2 from Nyall Dawson ---
yes, but in this case there's no way around calling the detaching [] operator
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=356699
Bug ID: 356699
Summary: detaching-member: don't warn when non-const method is
called on item
Product: clazy
Version: unspecified
Platform: Other
OS: Linux
14 matches
Mail list logo