https://bugs.kde.org/show_bug.cgi?id=358519
Sergio Martins changed:
What|Removed |Added
Latest Commit||http://commits.kde.org/claz
https://bugs.kde.org/show_bug.cgi?id=358519
Sergio Martins changed:
What|Removed |Added
Assignee|unassigned-b...@kde.org |smart...@kde.org
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=358519
Sergio Martins changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
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 #3 from Sergio Martins ---
for virtual classes it's important to have a non-inline dtor, even if empty,
for value classes no.
but ok, it reduces the amount of noise, and if it's empty it wouldn't be hiding
a bug anyway
--
You are receiving
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
--- Comment #1 from Sergio Martins ---
why do you have an empty dtor ?
--
You are receiving this mail because:
You are watching all bug changes.
