On Montag, 16. November 2020 02:53:14 CET Thiago Macieira wrote:
> On Sunday, 15 November 2020 08:29:56 PST Thiago Macieira wrote:
> > > * whether there is any chance to get a fix or workaround in the near
> > > future
> > > (or even right now), either in the form of an upgrade to the vendor
> > >
> On 13 Nov 2020, at 18:49, Thiago Macieira wrote:
>
> On Friday, 13 November 2020 00:19:41 PST Lars Knoll wrote:
>> I would hope that we’ll get mechanism to move them and help from the
>> compiler and/or C++ standard here. This is especially needed for
>> relocatable objects, as that makes a h
> > One problem with it is that it doesn’t support std::future or std::invoke.
> > See https://bugreports.qt.io/browse/QTBUG-88392
> >
> > So how about it, do we want to support that?
> See the other thread.
> We wait for them to support those.
Oh man how did I miss that one. Sorry :/
On Sunday, 15 November 2020 21:35:59 PST Tony Sarajärvi wrote:
> One problem with it is that it doesn’t support std::future or std::invoke.
> See https://bugreports.qt.io/browse/QTBUG-88392
>
> So how about it, do we want to support that?
See the other thread.
We wait for them to support those.
Hi,
I’ve been experimenting with getting builds on Windows done with LLVM. I’m
trying to use the package from winlibs.com and to be more precies, this one:
https://github.com/brechtsanders/winlibs_mingw/releases/download/10.2.0-10.0.1-9.0.0-r1/winlibs-x86_64-posix-seh-gcc-10.2.0-llvm-10.0.1-ming
On Sunday, 15 November 2020 08:29:56 PST Thiago Macieira wrote:
> > * whether there is any chance to get a fix or workaround in the near
> > future
> > (or even right now), either in the form of an upgrade to the vendor
> > compiler or in the form of a third-party compiler (e.g., GCC or Clang,
> >
On 15/11/2020 01:37, Thiago Macieira wrote:
Anyway, the question remains: can we remove the configure-time check and
assume std::future and std::async (C++11 standard library features) are
present?
The alternative is reimplement QThread::create in a way that doesn't
need async/future at all.
On Sunday, 15 November 2020 04:34:49 PST Kevin Kofler via Development wrote:
> Thiago Macieira wrote:
> > At least one platform -- not a main one -- will stop working.
>
> IMHO, it would be useful in such cases to specify which platform you are
> talking about, so others can get a better picture o
On Sonntag, 15. November 2020 01:37:32 CET Thiago Macieira wrote:
> On Saturday, 14 November 2020 03:05:13 PST Giuseppe D'Angelo via Development
> wrote:
> > 2) was removed in https://codereview.qt-project.org/c/qt/qtbase/+/306811
> > , or are you referring to something else? Was it a mistake to re
