Thiago Macieira wrote in
news:2865734.Ex9A2HvPv6@tjmaciei-mobl5:
> * because our builds are labelled "msvc2019"
Does the label reflect the compiler used? (I know 2019 and 2022 are binary
compatible.)
I haven't bothered to build the most recent 5.15.x open source version, but
back at
Requirement: the qHash function in question is and has always been out-of-
line. We obviously can't change the hashing function of inline code, because
it may have been inlined.
When the seed is non-zero, we make no guarantees on what the result will be.
The result is allowed to change between
On Tuesday, 2 May 2023 17:39:01 PST Thiago Macieira wrote:
> I don't have access to QNX and INTEGRITY toolchain information, so I'd like
> to request that they simply match the feature list above, with minimal
> workarounds.
What's the current state for those, for supporting Qt 6.8 or 6.9?
We
On Wednesday, 21 December 2022 09:51:52 PST Vladimir Minenko via Development
wrote:
> We got four user stories on Qt Bug Reports:
>
> 1. Use C++20 code with Qt - https://bugreports.qt.io/browse/QTBUG-109360
> 2. C++20 is required for the development of Qt itself -
>
The compiler is pretty buggy and has several, unfixed conformance issues with
C++.
One year ago I asked on the interest mailing list about using a non-latest
MSVC:
https://lists.qt-project.org/pipermail/interest/2023-January/038859.html
The reasons reported for not going to the next were:
*
