I really like the idea. Do we could add std::string_view too? [?]
From: Qt-creator on
behalf of Eike Ziller
Sent: Wednesday, August 24, 2016 1:57:45 PM
To: qt-creator@qt-project.org
Subject: [Qt-creator] Proposal: Adding std::(experimental::)optional
Proposal:
On November 28, 2016 19:03:57 "Jason A. Donenfeld" wrote:
> Hello All,
>
> Responses to each of you are inline below.
>
> Sounds to me like there's a lot of work to be done, still, and I
> haven't received any enthusiastic responses from the Qt team of, "yes!
> we'd love to work on this and mak
+1
It fixes many annoying bugs too!
I would like to use auto for return types if they are returning long types like
iterators, tuples, pairs or a mixture of them.
Something like
std::pair::const_iterator, bool> findEntry(const
std::pair &items, int value)
{
auto found = std::lower_b
Hi
I would imagine something like in this video:
https://youtu.be/JSjoCisIHcM
Minute 23
On 21 August 2017 8:18:25 PM Timur Kristóf wrote:
> Hi,
>
> I noticed that the built-in code style options somewhat clash with the
> beautifier plugin. (I notice that the code style settings don't affect
>
We are looking into implementing the language server protocol but that is not
so important now.
For the speed problem, we have an idea how we can improve it but we don't want
to add it in 4.6 because it could can break something.
From: Qt-creator on
behalf of
> Well, there are things that are hard to report via survey, e.g. rate of
> crashes or memory leaking in clangbackend
We have a crash handler in the works, which is much more useful than this. And
memory leaks can simply be investigated simply by debugging. I don't see how
this plugin could he
It would be nice if you can explain what data you want to collect and how it
will be help the creator development. In my view it is quite hard to collect
data about not implemented features, so you could only provide information
about what feature is used. So the data could be used to see what s
Edward Welbourne:
> When you look into the feature that no-one uses much, you may find that most
> users
> that do use it have a crash report following close on the heels of their
> use of it; you can make an educated guess at why they don't use it after that.
We have already a crash reporter,
r instance where we can send the crash
dumps.
From: Development on
behalf of Marco Bubke
Sent: Monday, February 26, 2018 6:29:22 PM
To: Edward Welbourne; Robert Loehning; André Pönitz
Cc: developm...@qt-project.org; Ryein Goddard; qt-creator@qt-project
Hi
You cannot set MSVC 2017 Version 15.8 to C++11, only C++14 or C++17 is
possible. If you set it to C++11 you should get C++17.
From: Qt-creator on
behalf of Nikolai Kosjar
Sent: Thursday, November 15, 2018 4:33:50 PM
To: Julius Bullinger; qt-creator@qt-proj
Hi Michael, if we add more threads we will waste more memory and the code
complexity goes up too. I don't work on this code anymore but there will be
always trade offs between speed, memory and code complexity (which increases
maintenance time and reduces new feature time). So you want to do the
We collect the diagnostics as we compiling the translation unit for completion,
highlighting etc.. But the compiling is slower because it takes time to find
all the warnings, some are actually quite cheap but other are very expensive to
compute. An other idea was only to generate diagnostics for
With modules hopefully the split in header and source files will go away in the
long run.
On March 1, 2019 14:29:00 Jason H wrote:
> Excellent. It's rather buried though. 3 clicks for singing I'd use _many_
> times a day?
>
> I've been wondering if it would be better to have a tool that takes
Clang could explicitly instantiate the default time and use it for code
completion but this has to be done in Clang. If you could provide a patch to
Clang we would automatically use it. ;-)
From: Qt-creator on behalf of علی موسوی
Sent: Thursday, March 14, 2019
Looks a little bit like copy 'n paste programming on steroids. ;-)
On 29/07/2019 17:02, Jason H wrote:
> Slashdot is running a sotrry bout an AI-powered editor extension Deep
> TabNine. https://tabnine.com/blog/deep
> This seems to work via the language server protocol. IT pposts Python and C++
Hi Michael
There is already a bug report:
https://bugreports.qt.io/browse/QTCREATORBUG-23349
So there is in my opinion no need to start a email thread too. ;-)
Best, Marco
On 25/03/2020 16:28, Michael Jackson wrote:
Back in the QtCreator 4.10 days there was "automatic" clang-tidy/clazy
int
Hi
C++ 20 produces much less code if you combine simple structs and emplace_back.
Before C++ 20 you have to add a constructor which can easily double the code.
It is a simple feature but can have big advantages.
From: Qt-creator on behalf of apoenitz
Sent: Mon
17 matches
Mail list logo