On Friday, 5 March 2021 04:40:24 PST Lars Knoll wrote:
> I wish we had a good way of adding that overloaded constructor to QString.
> Unfortunately, we have lots of API that is overloaded on both QString and
> QStringView. Adding the constructor to QString will then cause ambiguities
> wherever we
Il 05/03/21 13:51, Andrei Golubev ha scritto:
That said, QByteArray's ctor accepting char* is not explicit (which kind
of makes sense) and we have this ambiguity for f(QByteArray) and
f(QByteArrayView) I believe. But guessing that it's not expected that
QByteArrayView would be as popular as QSt
That said, QByteArray's ctor accepting char* is not explicit (which kind of
makes sense) and we have this ambiguity for f(QByteArray) and f(QByteArrayView)
I believe. But guessing that it's not expected that QByteArrayView would be as
popular as QStringView.
Thus, QByteArray str = "hello" works
On 5 Mar 2021, at 12:08, Tor Arne Vestbø
mailto:tor.arne.ves...@qt.io>> wrote:
On 3 Mar 2021, at 16:53, Andrei Golubev
mailto:andrei.golu...@qt.io>> wrote:
QString hello = u"Hello"; // oops, compilation error
This seems like a bug though? From an API point of view, I’d expect this simple
ass
On Fri, 5 Mar 2021 at 14:26, Giuseppe D'Angelo via Development
wrote:
>
> Il 05/03/21 12:08, Tor Arne Vestbø ha scritto:
> > This seems like a bug though? From an API point of view, I’d expect this
> > simple assignment to JustWorkTM, without requiring syntactic sugar all
> > over the place. Shoul
Il 05/03/21 12:08, Tor Arne Vestbø ha scritto:
This seems like a bug though? From an API point of view, I’d expect this
simple assignment to JustWorkTM, without requiring syntactic sugar all
over the place. Shouldn’t we fix this, so we don’t need (or leave
optional) an explicit _qs suffix?
Be
On 3 Mar 2021, at 16:53, Andrei Golubev
mailto:andrei.golu...@qt.io>> wrote:
>> QString hello = u"Hello"; // oops, compilation error
Tor Arne Vestbø (5 March 2021 12:08) replied:
> This seems like a bug though? From an API point of view, I’d expect
> this simple assignment to JustWorkTM, without
On 3 Mar 2021, at 16:53, Andrei Golubev
mailto:andrei.golu...@qt.io>> wrote:
QString hello = u"Hello"; // oops, compilation error
This seems like a bug though? From an API point of view, I’d expect this simple
assignment to JustWorkTM, without requiring syntactic sugar all over the place.
Sho
For anyone interested, here's a patch:
https://codereview.qt-project.org/c/qt/qtbase/+/337616
--
Best Regards,
Andrei
From: Development on behalf of Thiago
Macieira
Sent: Wednesday, March 3, 2021 8:58 PM
To: development@qt-project.org
Subject: Re: [Development]
Good morning,
I was curious to see what changed in Qt 6.0.2 release and found a list of
fixed QTBUGS:
[qtbase]
443ce5d073 Fixes: QTBUG-89578
b61275ee72 Fixes: QTBUG-90042
e255716291 Fixes: QTBUG-74088
The QTBUG number itself does not tell me much, hence it is very hard to
predict if anything re
10 matches
Mail list logo
