git, gcc, Linux?
пт, 18 окт. 2019 г. в 00:25, Ville Voutilainen :
> On Fri, 18 Oct 2019 at 00:16, André Pönitz wrote:
> >
> > On Thu, Oct 17, 2019 at 09:04:36PM +0300, Ville Voutilainen wrote:
> > > Since we are about to do a major version upgrade, should be stop being
> > > a special snowflake
Can't it be alleviated/improved by providing user-defined literal for
QString(Literal)? So that one would only write a["b"_qs] = "c"_qs.
чт, 22 авг. 2019 г. в 21:57, André Pönitz :
> On Thu, Aug 22, 2019 at 08:48:30PM +0200, André Pönitz wrote:
> > On Thu, Aug 22, 2019 at 05:39:07PM +0200, Mutz
Isn't it already the case: https://doc.qt.io/qt-5/supported-platforms.html
?
чт, 22 авг. 2019 г. в 18:10, Thiago Macieira :
> On Wednesday, 21 August 2019 17:17:17 PDT Kevin Kofler wrote:
> > > So let me instead change my request:
> > > Can we require GCC 8 for MinGW for Qt 5.15?
> >
> > This i
I see that situation has improved somewhat since I've last tried to use
cppreference qch in Qt Creator about a year ago, but the formatting still
sometimes goes crazy (especially with "since C++XY" in the overload list),
and there are some issues with font aliasing. I.e. there are definitely
many w
> The converse (always having to write `.second`, not to mention the
*name* "second") has its own annoyances.
You don't have to write that:
for (const auto &[key, value] : m)
вт, 11 июн. 2019 г. в 22:22, Matthew Woehlke :
> On 04/06/2019 16.41, Mutz, Marc via Development wrote:
> > On 2019-06-0
Have you tried running the script with "powershell –ExecutionPolicy Bypass"
? IRC, this should work for regular non-admin users to. If that does work,
I think you can just pipe the script to "powershell -".
вт, 4 июн. 2019 г. в 01:54, Thiago Macieira :
> On Saturday, 1 June 2019 08:14:13 PDT Jean
Exhibit C:
foo().contains(x)
https://godbolt.org/z/KlIcFc
пн, 20 мая 2019 г. в 23:14, André Pönitz :
> On Fri, May 17, 2019 at 10:17:10AM +0200, Mutz, Marc via Development wrote:
> > [...] There is no readability difference between the use of a Qt
> container and
> > that of an STL container.
>
> When selecting this operating system which we created packages with, we
tend to select a reasonable new one, most preferably a stable one, with a
good set of old libraries so that the backwards compatibility is good. Take
RHEL 7 for example. RHEL 7.0 was release in June 2014. In July 2017 we got
