Re: [Development] Houston, qint128 has a problem

2024-08-25 Thread Ville Voutilainen
On Sat, 9 Dec 2023 at 18:16, Thiago Macieira wrote: > > On Friday, 8 December 2023 18:51:19 PST Marc Mutz via Development wrote: > > After spending countless hours between Ivan and myself fighting GCC's > > mysteriously-vanishing support for __int128_t (= qint128), > > it turns out that with -ans

Re: [Development] QVariant and types with throwing dtors

2024-08-25 Thread Ville Voutilainen
On Mon, 26 Aug 2024 at 08:26, Marc Mutz via Development wrote: > My vote goes to (3). (2) is a good intermediate step (e.g. for Qt 6, > with Qt 7 converting to static_assert()). Remember that ctors are > implicitly noexcept in C++, so you need to do actual work to make a type > that's not nothrow_

[Development] Bye, bye, qsnprinttf()

2024-08-25 Thread Marc Mutz via Development
Hi, During my vacation, the last bits of my qsnprintf() work have merged. The user-visible changes are: - qsnprinf() has gained the __attribute__((format(printf))) it has been lacking since its inception, so -Wformat now works (and has caught some problems in Qt). The attribute has been pi

Re: [Development] QVariant and types with throwing dtors

2024-08-25 Thread Marc Mutz via Development
(sorry for the late entrance, was OOO the last two weeks) My vote goes to (3). (2) is a good intermediate step (e.g. for Qt 6, with Qt 7 converting to static_assert()). Remember that ctors are implicitly noexcept in C++, so you need to do actual work to make a type that's not nothrow_destructib