Feature request to run clang-tidy on JUCE code with as many checks turned on as makes sense to the project.
I’ve just successfully run it myself on a project for the first time, with the help of FRUT, and got a lot of warnings on JUCE code, even when I just turned on the analyzer warnings using
For example, it seems
StandalonePluginHolder::createPlugin() should not be
virtual (or altenatively, not be called from the constructor as it is right now).
It would be great to have JUCE’s code
clang-tidyed to be able to then look at our own