-
-
Notifications
You must be signed in to change notification settings - Fork 392
clang-tidy: check and fix cppcoreguidelines-pro-bounds-array-to-pointer-decay #3074
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
Open
prashsti29
wants to merge
5
commits into
pgRouting:develop
Choose a base branch
from
prashsti29:prashsti29-clang-tidy
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
7773b94
clang-tidy: check and fix cppcoreguidelines-pro-bounds-array-to-point…
prashsti29 dd9a062
fix warnings in binaryBreadthFirstSearch_driver.cpp
prashsti29 edae3d3
fix warnings in assert.cpp
prashsti29 8e11980
Trigger GitHub Actions
prashsti29 a09c733
Remove temporary CI trigger file
prashsti29 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧹 Nitpick | 🔵 Trivial
Consider
std::data(trace)as a cleaner alternative tostatic_cast<void**>(trace).An LLVM bug report on the same
backtrace_symbolspattern confirms thatstatic_cast<void**>resolves the array-to-pointer decay warning, so the fix is correct. However, the idiomatic C++17 way to explicitly obtain a pointer to an array's first element without a cast isstd::data():♻️ Optional refactor using `std::data()`
Both approaches silence the clang-tidy check because the check was patched to not flag explicit casts. The
std::data()form expresses the intent (pointer to the first element) more directly than astatic_cast.📝 Committable suggestion
🤖 Prompt for AI Agents