> -Original Message-
> From: Edward Welbourne
> Sent: maanantai 25. toukokuuta 2020 16.52
> To: Jani Heikkinen
> Cc: Qt development mailing list ; Ville
> Voutilainen ; Thiago Macieira
>
> Subject: Re: [Development] Drop MSVC 2015 in Qt 5.15?
>
> I don't think the pre-release builds need
Il 25/05/20 17:40, Thiago Macieira ha scritto:
On Monday, 25 May 2020 04:37:26 PDT Edward Welbourne wrote:
The "comparisons" heading might stretch as far as using a UTF-8 key to
do a look-up in a QString-keyed hash,
Using UTF-8 data to look up in a QString-keyed hash will require conversion to
On Monday, 25 May 2020 04:37:26 PDT Edward Welbourne wrote:
> The "comparisons" heading might stretch as far as using a UTF-8 key to
> do a look-up in a QString-keyed hash,
Using UTF-8 data to look up in a QString-keyed hash will require conversion to
UTF-16 to calculate the hash. It can't be cal
On 25/05/2020 07.37, Edward Welbourne wrote:
I would just call it QUtf8View, since (see below) I don't see value in a
separate QUtf8String for it to be a view into
On the one hand...
std::string_view is not a view into a std::string. A std::string is a
*container* for text, a std::string_view
On Friday, 22 May 2020 02:21:29 PDT Tony Sarajärvi wrote:
Now open for discussion:
https://bugreports.qt.io/browse/QTQAINFRA-3745 Based on Thiago’s
comment that we don’t want to keep supporting it for years:
https://codereview.qt-project.org/c/qt/qtdoc/+/269546
On Sat, 23 May 2
Thiago Macieira (23 May 2020 03:06) wrote:
> Update:
>
> As we're reviewing the changes Lars is making to get rid of
> QStringRef, Lars, Marc and I came to the conclusion that
> QUtf8StringView is required for Qt 6.0.
[snip]
Sounds sensible.
I would just call it QUtf8View, since (see below) I don'
On 5/25/20 8:51 AM, Tony Sarajärvi wrote:
Or are you having new features coming in 5.15.1+ that would require additional
coding to make it MSVC 2015 compatible?
I strongly hope that there are *no* new features in patch releases. The
question is mostly whether you want to support MSVC 2015 in
