Am Mittwoch, 6. November 2019, 16:13:28 CET schrieb David Edmundson:
> >Any chance this is about KGamma and you ran clazy with a Qt 5.14 copy
> >locally?
> It was!
Okay :) So no new holes to fix then discovered.
> >So here repeating the recommendation done by a few, which project
> >maintainers
>Any chance this is about KGamma and you ran clazy with a Qt 5.14 copy locally?
It was!
>so the compiler still sees the overload and throws up.
Yeah, the whole situation makes total sense, it just wasn't something
that I had thought about when blindly running clazy.
>So here repeating the
Am Mittwoch, 6. November 2019, 14:14:41 CET schrieb David Edmundson:
> I just found a slight issue when using _DEPRECATED_SINCE.
>
> If one of two overloaded Q_SIGNALS is deprecated, clazy will blindly
> port the signal without an overload as to the compiler only one signal
> exists. This then
Am Mittwoch, 6. November 2019, 14:14:41 CET schrieb David Edmundson:
> I just found a slight issue when using _DEPRECATED_SINCE.
>
> If one of two overloaded Q_SIGNALS is deprecated, clazy will blindly
> port the signal without an overload as to the compiler only one signal
> exists. This then
I just found a slight issue when using _DEPRECATED_SINCE.
If one of two overloaded Q_SIGNALS is deprecated, clazy will blindly
port the signal without an overload as to the compiler only one signal
exists. This then gives a compilation error at a distro/CI level.
I don't think anything can be
Hi,
with KF 5.64 now branched and thus the new deprecation macros going to be
released for the first time, now please make sure when in the future marking
API as deprecated to use the correct current version, i.e. the one where the
deprecation will be made public the first time.
So if pushing
