> On 11 Jun 2020, at 12:56, Lars Knoll wrote:
>
> We certainly shouldn’t start documenting the macros now in 5.15.1.
Fine by me; I’ve abandoned the documentation effort and closed the reported bug
as won’t do.
--
Paul Wicking
R Manager
The Qt Company
Sandakerveien 116
0484, Oslo,
Il 11/06/20 11:11, Edward Welbourne ha scritto:
That then leaves the question of whether we deprecate in Qt 6 or remove
these macros. I shall leave Marc, who I understand as wanting the
latter option, to make the case for it, lest I misrepresent that case.
I fear the macros are going to be
We certainly shouldn’t start documenting the macros now in 5.15.1.
IMO they should simply unconditionally expand to static_assert(). I’d also be
ok if someone wants to do a search and replace s/Q_STATIC_ASSERT/static_assert/
in our source code.
But I don’t think we should do much more right
Hi,
I don't care much about when we remove these macros, as it makes sense
to keep using them in Qt 6 for code that will be backported to 5.
What I don't agree with is to go to extra lengths to deprecate (that
would be cutting our own flesh, if we retain the macros for the
above-mentioned
On 11/06/20 11:11, Edward Welbourne wrote:
Hi all,
On [0] there is discussion of deprecating these two macros, or even
outright removing them in Qt 6. I see the sense of deprecation, on dev
at least, since we expect C++17, in which static_assert() does the whole
job. Since they're macros, I
Hi all,
On [0] there is discussion of deprecating these two macros, or even
outright removing them in Qt 6. I see the sense of deprecation, on dev
at least, since we expect C++17, in which static_assert() does the whole
job. Since they're macros, I know of no way to tell the compiler to
warn
