On 2017-05-25 01:19, Ville Voutilainen wrote:
[...]
How does it help anyone to create a new alias that still results in a
concrete type
the semantics of which still depend on the element type?
The QList type alias in Qt 6 would be deprecated from the get-go. As
would be the QArrayList/QVector
On 24 May 2017 at 22:25, Marc Mutz wrote:
> On 2017-05-24 15:12, Konstantin Tokarev wrote:
>>
>> 24.05.2017, 15:49, "NIkolai Marchenko" :
>>>
>>> A semi-sane idea that I think no one has suggested yet:
>>>
>>> What if, starting from Qt6, QList becomes
On Wednesday, 24 May 2017 12:09:41 PDT Marc Mutz wrote:
> I maintain that they were forgotten. Well, or ignored.
>
> From a quick grep in QtBase, two that caught my eye:
>
> - qvector.h: The solution is obvious, straight-forward, and BiC:
>unexport QPolygon(F). Wasn't done. Wouldn't've
On 2017-05-24 15:12, Konstantin Tokarev wrote:
24.05.2017, 15:49, "NIkolai Marchenko" :
A semi-sane idea that I think no one has suggested yet:
What if, starting from Qt6, QList becomes a wrapper for QArrayList
with a contructor from this type?
After all making
On 2017-05-24 18:40, Thiago Macieira wrote:
On Wednesday, 24 May 2017 02:04:36 PDT Lars Knoll wrote:
> On 24 May 2017, at 00:35, Giuseppe D'Angelo wrote:
>
> On Tue, May 23, 2017 at 11:56 PM, Thiago Macieira
>
> wrote:
>> We are arguing whether
On Wednesday, 24 May 2017 02:04:36 PDT Lars Knoll wrote:
> > On 24 May 2017, at 00:35, Giuseppe D'Angelo wrote:
> >
> > On Tue, May 23, 2017 at 11:56 PM, Thiago Macieira
> >
> > wrote:
> >> We are arguing whether the change makes the code uglier
On Tuesday, 23 May 2017 15:35:50 PDT Giuseppe D'Angelo wrote:
> On Tue, May 23, 2017 at 11:56 PM, Thiago Macieira
>
> wrote:
> > We are arguing whether the change makes the code uglier and is worth that
> > ugliness. I'm not sold on that. Leave those const behind until
We seem to have hardware issues which are under investigation. We'll be back
online as soon as possible.
-Tony
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Not necessarily. It really depends on which type Qt decides to use in place
of what is now returned as a QList.
As far as wrapper is concerned, it doesn't even need to be a singlular type
if the interface matches since it will be a template anyway.
P.S. I am not really involved with Qt
24.05.2017, 16:19, "NIkolai Marchenko" :
> I was talking about the solution that assumes making a QArrayList type and
> deprecating QList entirely,
> not the one that aliases QList to QVector which I, personally, don't like,
> since it will produce a lot of the code
I was talking about the solution that assumes making a QArrayList type and
deprecating QList entirely,
not the one that aliases QList to QVector which I, personally, don't like,
since it will produce a lot of the code perception problems and incorrect
perfomance assumptions.
Not to mention people
24.05.2017, 15:49, "NIkolai Marchenko" :
> A semi-sane idea that I think no one has suggested yet:
>
> What if, starting from Qt6, QList becomes a wrapper for QArrayList with a
> contructor from this type?
> After all making existing code slightly _slower_ because of
Hi all,
We have released Qt 5.9.0 RC today. You can update it at the top of your Qt 5.9
beta(4) online installation or do clean installation by using qt online
installer. Detailed instructions here:
https://wiki.qt.io/How_to_get_snapshot_via_online_installer .
Qt 5.9.0 RC is also available as
Hi all,
Qt 5.9.0 RC is now available. Diff to beta4 can be found as an attachment.
You can update RC at the top of existing online installation by using
maintenance tool or do clean installation. Instructions how to get the release
via online installer are here:
> On 24 May 2017, at 00:35, Giuseppe D'Angelo wrote:
>
> On Tue, May 23, 2017 at 11:56 PM, Thiago Macieira
> wrote:
>>
>> We are arguing whether the change makes the code uglier and is worth that
>> ugliness. I'm not sold on that. Leave those
15 matches
Mail list logo