Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warning Cleanup #342

Merged
merged 72 commits into from
May 5, 2021
Merged

Warning Cleanup #342

merged 72 commits into from
May 5, 2021

Conversation

yeetari
Copy link
Member

@yeetari yeetari commented Apr 7, 2021

This PR cleans up all of the current clang-tidy warnings to allow us to add a clang-tidy CI. There are a few other key changes in the PR such as switching our clang-tidy config style from enabling all checks, and then disabling ones we don't want to just enabling ones we want. This avoids the problem of new clang-tidy versions introducing new checks which we don't want.

Closes #341

@IAmNotHanni IAmNotHanni added the cat:refactor refactor/clean up/simplifications/etc. label Apr 8, 2021
@IceflowRE
Copy link
Member

IceflowRE commented Apr 8, 2021

This avoids the problem of new clang-tidy versions introducing new checks which we don't want.

On the other side we have to get active from our side when a new version was released. If we stay with the our current system we will get it, if new checs were added, most of the time.

@yeetari
Copy link
Member Author

yeetari commented Apr 8, 2021

On the other side we have to get active from our side when a new version was released. If we stay with the our current system we will get it, if new checs were added, most of the time.

True, but most of the new checks introduced (and most of the current checks in total) are guidelines for specific projects that we don't want. For example, making sure symbols are in the abseil/llvmlibc namespace.

@yeetari yeetari force-pushed the yeetari/warning-cleanup branch 16 times, most recently from 77b36e1 to 78e5665 Compare April 17, 2021 20:54
@yeetari yeetari added the prio:blocker this issue cannot be moved to a later milestone, also this label cannot be removed label Apr 17, 2021
@yeetari yeetari force-pushed the yeetari/warning-cleanup branch 4 times, most recently from 86e65be to 7bbbe80 Compare April 17, 2021 21:50
@yeetari yeetari marked this pull request as ready for review April 17, 2021 21:57
.github/workflows/static_analysis.yml Show resolved Hide resolved
src/vulkan-renderer/application.cpp Outdated Show resolved Hide resolved
src/vulkan-renderer/application.cpp Outdated Show resolved Hide resolved
src/vulkan-renderer/world/cube.cpp Show resolved Hide resolved
@yeetari yeetari merged commit 788a94b into master May 5, 2021
@yeetari yeetari deleted the yeetari/warning-cleanup branch June 11, 2021 16:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cat:refactor refactor/clean up/simplifications/etc. prio:blocker this issue cannot be moved to a later milestone, also this label cannot be removed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fix clang-tidy and msvc static code analysis warnings before adding clang-tidy to continuous integration
4 participants