> On Feb 14, 2018, at 5:00 AM, Guenter Schwann wrote:
>
> On Mittwoch, 14. Februar 2018 13:47:51 CET Konstantin Tokarev wrote:
>> 14.02.2018, 03:04, "Steve Atkins" :
On Feb 13, 2018, at 4:00 PM, Nikos Chantziaras wrote:
tor-bounces+marco.bubke=qt...@qt-project.org> on
behalf of Nikos Chantziaras <rea...@gmail.com>
Sent: Wednesday, February 14, 2018 6:05:36 PM
To: qt-creator@qt-project.org
Subject: Re: [Qt-creator] clangbackend slow code completion
Shouldn't all this actually be using clangd?
https://cl
Shouldn't all this actually be using clangd?
https://clang.llvm.org/extra/clangd.html
On 14/02/18 15:08, Ivan Donchevskii wrote:
Btw. - it would be nice if the QtCreator clang-tidy plugin would
(optionally)
make use of a .clang-tidy config file (to share it with clang power
tools for
@qt-project.org> on
behalf of Guenter Schwann <guenterli...@schwann.at>
Sent: Wednesday, February 14, 2018 2:00 PM
To: qt-creator@qt-project.org
Subject: Re: [Qt-creator] clangbackend slow code completion
On Mittwoch, 14. Februar 2018 13:47:51 CET Konstantin Tokarev wrote:
> 14.02.2018
On Mittwoch, 14. Februar 2018 13:47:51 CET Konstantin Tokarev wrote:
> 14.02.2018, 03:04, "Steve Atkins" :
> >> On Feb 13, 2018, at 4:00 PM, Nikos Chantziaras wrote:
> >>
> >> If you have the "clang-tidy" checks enabled, disable them, or only use 1
> >> or
14.02.2018, 03:04, "Steve Atkins" :
>> On Feb 13, 2018, at 4:00 PM, Nikos Chantziaras wrote:
>>
>> If you have the "clang-tidy" checks enabled, disable them, or only use 1 or
>> 2 of them. That feature is extremely slow.
>
> That fixes it, thanks. Bit of
> On Feb 13, 2018, at 4:00 PM, Nikos Chantziaras wrote:
>
> If you have the "clang-tidy" checks enabled, disable them, or only use 1 or 2
> of them. That feature is extremely slow.
That fixes it, thanks. Bit of a shame, as they were rather a nice feature.
Cheers,
Steve
>
If you have the "clang-tidy" checks enabled, disable them, or only use 1
or 2 of them. That feature is extremely slow.
On 14/02/18 01:33, Steve Atkins wrote:
I'm using Creator 4.6.0-beta1 on a current generation macbook pro, and code
completion is painfully slow - it'll take four or five