https://bugs.kde.org/show_bug.cgi?id=358799
--- Comment #10 from Igor Kushnir <igor...@gmail.com> --- (In reply to Piotr Mierzwinski from comment #9) > So the fix breaks different use case. But why does it break a use case? Your proposed alternative of removing the previous default parameter value can be a loss of information, especially if the code in question has not been put under version control yet. Adding a frequently valid and reasonable new default parameter value does not lose information. The TODO marker suggests the user to consider what the default value should be. If the user prefers no default values whatsoever, (s)he can remove both the new and the old one easily. Again the TODO marker reminds the user about this. I don't think the current behavior is much worse than showing a warning. Showing a warning is probably more difficult to get right (a nested event loop or code scattered across several functions). -- You are receiving this mail because: You are watching all bug changes.
