Integrate clang-tidy
configuration into nix and CI #147
Labels
No labels
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/store
bug
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
RFD
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
ux
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#147
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We can run clang-tidy on nix and potentially find some bugs. Let's get a config file going and run it in CI.
This actually depends on meson in practice because of compile_commands.json.
it appears this requires almost no work besides fixing the things the linter finds, once meson is in place. https://mesonbuild.com/Release-notes-for-0-52-0.html#clangtidy-target
we can also ban VLAs
To make effective progress on fixing the warnings if we actually turn them all on, I think we might want to consider hosting something like https://github.com/Ericsson/codechecker and then integrating it into buildbot, taking the reports from the nix build and uploading them somewhere.
This issue was mentioned on Gerrit on the following CLs: