[Qt-creator] QtCreator 4.9 and Clang Tidy Feedback

[Michael Jackson]

I’m still contending (without any idea of how hard it would be to implement, let alone the UX to let the user know what is going on) that the creation of the function drop down should be separate from the clang-tidy run. Do the function drop down first. Then start the clang-tidy run. Would be neat to have some sort of “indicator” icon to say that clang-tidy was running or completed. I can wish…. 

 

--

Mike Jackson 

 

From: Andy <asmaloney at gmail.com>
Date: Wednesday, February 20, 2019 at 9:40 AM
To: Michael Jackson <mike.jackson at bluequartz.net>
Cc: Nikolai Kosjar <Nikolai.Kosjar at qt.io>, Qt-creator <qt-creator at qt-project.org>
Subject: Re: [Qt-creator] QtCreator 4.9 and Clang Tidy Feedback

 

FWIW - I'll add a "Me too".

 

Some files I'm working with take 25-30 seconds to process & show their list of methods in the dropdown.

 

If there were an (easy) way to figure out which Tidy options were slowest even that would help. Then I could make intelligent decisions about what to keep using.

 

---
Andy Maloney  //  https://asmaloney.com

twitter ~ @asmaloney

 

 

 

On Wed, Feb 20, 2019 at 8:36 AM Michael Jackson <mike.jackson at bluequartz.net> wrote:

 

On Wed, Feb 20, 2019 at 3:14 AM Nikolai Kosjar <Nikolai.Kosjar at qt.io> wrote:

On 2/19/19 3:19 PM, Michael Jackson wrote:
> Started using the 4.9 betas last week and generally I like the 
> improvements. I do like the idea of moving the clang-tidy to the 
> “Analyze” menu in order to make it easier to get to.

It was already in that menu since version 4.7. And before that it was 
also there, but as "Clang Static Analyzer" :)

 


> Could we get a 
> “Clang-Tidy current File” (in the same idea as Beautifier plugin has 
> Clang-Format current file).

Sounds useful. https://bugreports.qt.io/browse/QTCREATORBUG-22008 was 
just created for this.

Another one that might be useful is "Analyze the touched files of last N 
commits."

Nikolai

 

Yes, I would take either one right now. Our current code base was written almost 10 years ago and until about 2017 one of our collaborators was stuck VS 2010 so there was almost _no_ use of C++11, let alone GSL, C++14 and all of the recommended modern programming styles. As we update each file for bugs we like to have all of the clang-tidy warnings show up to remind us what needs to be updated. The downside is just having to wait what seems like forever for the functions menu to become available. I look forward to seeing a few more "quality of life" improvements in this area added into the next version.

 

--

Mike Jackson

_______________________________________________
Qt-creator mailing list
Qt-creator at qt-project.org
https://lists.qt-project.org/listinfo/qt-creator

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qt-creator/attachments/20190220/9fc929b2/attachment-0001.html>