D8959: Make more signals non-const
Friedrich W. H. Kossebau
noreply at phabricator.kde.org
Thu Nov 23 00:28:38 UTC 2017
kossebau created this revision.
kossebau added a reviewer: KDevelop.
Restricted Application added a subscriber: kdevelop-devel.
Not sure exactly what is wrong with const signals, besides
QMetaObject::activate(...) wanting a non-const this argument.
Collected signals are from a recent clazy run, so changing these will at least
result in less noisy future clazy run ;)
And perhaps consistency in general signal non-constness.
The Clazy const-signal-or-slot check docs only claims
"For signals, it's just pointless to mark them as const."
without giving any reasoning.
So dumping patch as RFC, to be either moved to /dev/null or applied.
To: kossebau, #kdevelop
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the KDevelop-devel