I tend to go back and forth between turning it off so that code completion actually completes in a reasonable amount of time (~1 second) or having all the helpful insights into my code base. It is almost like QtCreator needs to have 2 threads running. One for the code completion and one for the clang-tidy stuff.
-- Mike Jackson On 6/13/18, 3:44 AM, "Qt-creator on behalf of Ivan Donchevskii" <[email protected] on behalf of [email protected]> wrote: Hi! On the contributors summit I mentioned that we want to introduce the "default" set of flags for Clang-Tidy which can be used as a starting point for analysis and is good enough for some random project developed in Qt Creator. We have an example of it in https://codereview.qt-project.org/#/c/230400/ but not sure if it is actually the proper list. Here's the list itself - "bugprone-*,cppcoreguidelines-*,misc-*,modernize-*,performance-*,readability-*,-cppcoreguidelines-owning-memory,-readability-braces-around-statements,-readability-implicit-bool-conversion,-readability-named-parameter" Let us know if there's something you would like to add or remove from it. You can check the whole tree of currently available checks in 4.7 beta or in one of our latest Qt Creator snapshots. Kind regards, Ivan _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
