On 2019-07-12 22:37, Matthew Woehlke wrote:
[...]
So, perhaps you should suggest a more specific example?
I did: replace and relational operators. And you're right to look at
startsWith(), because that is indeed binary (*this being the first
argument). And it's also one which is thoroughly vi
On 12/07/2019 16.05, Mutz, Marc via Development wrote:
> On 2019-07-12 17:27, Matthew Woehlke wrote:
>> On 11/07/2019 15.01, Thiago Macieira wrote:
> [...]
>>> Except that the whole point of those methods is that they can be more
>>> efficient when the encoding is known and therefore templating won
On 2019-07-12 17:27, Matthew Woehlke wrote:
On 11/07/2019 15.01, Thiago Macieira wrote:
[...]
Except that the whole point of those methods is that they can be more
efficient when the encoding is known and therefore templating won't
help.
So those cases can employ specializations. Or, perhaps
Hi Volker,
A few comments - I wrote the original policy and I'm happy that you're
taking the time to evolve it:
> In addition, we have also been discussing a few aspects in The Qt Company
> where we would like to see the policy evolve, such as:
>
> * the integration of CVE handling into the pro
On 11/07/2019 15.01, Thiago Macieira wrote:
> On Thursday, 11 July 2019 13:41:49 -03 Matthew Woehlke wrote:
>> On 11/07/2019 05.05, Mutz, Marc via Development wrote:
>>> There is a cost associated with another string class, too, and it's
>>> combinatorial explosion. Even when we have all view types
On Thursday, 11 July 2019 13:41:49 -03 Matthew Woehlke wrote:
> On 11/07/2019 05.05, Mutz, Marc via Development wrote:
> > There is a cost associated with another string class, too, and it's
> > combinatorial explosion. Even when we have all view types
> > (QLatin1StringView, QUtf8StringView, QStri
Volker Hilsheimer (22 May 2019 11:01) wrote:
> the Qt Project Security Policy is currently documented as a wiki page
> at [1]. Since QUIPs are the official way to document processes, I’m
> proposing that we are moving the policy to a QUIP.
That was reviewed as
https://codereview.qt-project.org/c/m
+1
Disclamer: We work for the same company ;-)
Am 7/11/19 um 5:27 PM schrieb Paul Wicking:
>
> Hi all,
>
>
>
> I’d like to nominate Kavindra Palaraja as approver. She is a very
> active contributor and reviewer, in particular for documentation
> related changes, focusing on the Qt Automotive pl
