Hi, Arthur. Could you help me with a code review?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
+ bryanenriquegv, could you please take a look?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
RewriteFunctionParamAndReturnType previously relied on getPreviousDecl(),
this assumes a linear single-linked chain across function redeclarations.
When intermediate declarations are skipped by AST matchers (e.g. macro
expansions or excluded headers), the graph produces disconnected components,
leading to mismatched function signatures across files.
This CL switches to fct_decl->redecls() to emit direct edges to all
visible redeclarations, maintaining graph connectivity.
Edit > [format] to fit 72 columns.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Auto-Submit | +1 |
| Commit-Queue | +1 |
Hi, Rick. Could you help me with a code review?
RewriteFunctionParamAndReturnType previously relied on getPreviousDecl(),
this assumes a linear single-linked chain across function redeclarations.
When intermediate declarations are skipped by AST matchers (e.g. macro
expansions or excluded headers), the graph produces disconnected components,
leading to mismatched function signatures across files.
This CL switches to fct_decl->redecls() to emit direct edges to all
visible redeclarations, maintaining graph connectivity.
Edit > [format] to fit 72 columns.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
// Copyright 2026 The Chromium AuthorsIt's IMHO a bit confusing to put a test file directly into the third_party tree. We're doing a bunch of things to try to better manage and track all the variety of projects we have under third_party (eg. insisting on OWNERS, autoroll, etc.).
Is there perhaps an easy way to get the same test coverage without adding files under //third_party/? If this is the most pragmatic way to get important test coverage then I'm OK with it but you need to add a README.md file which explains why this is here and not really a new third-party dependency, and an OWNERS file - presumably just pointing at the tools/spanify OWNERS.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +0 |
// Copyright 2026 The Chromium AuthorsIt's IMHO a bit confusing to put a test file directly into the third_party tree. We're doing a bunch of things to try to better manage and track all the variety of projects we have under third_party (eg. insisting on OWNERS, autoroll, etc.).
Is there perhaps an easy way to get the same test coverage without adding files under //third_party/? If this is the most pragmatic way to get important test coverage then I'm OK with it but you need to add a README.md file which explains why this is here and not really a new third-party dependency, and an OWNERS file - presumably just pointing at the tools/spanify OWNERS.
I missed the file location during code review.
@sergio...@google.com => Can you please move it to: `tools/clang/spanify/tests/chrome/third_party/` instead?
| Auto-Submit | +1 |
Done, I've moved test file third_party/spanify_tests/ignored.h to tools/clang/spanify/tests/chrome/third_party/ignored.h and updated the includes. Could you help me with another review?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Forgot to addressed the comment. Test file is now in tools/clang/spanify/tests/chrome/third_party/ignored.h
Arthur SonzogniIt's IMHO a bit confusing to put a test file directly into the third_party tree. We're doing a bunch of things to try to better manage and track all the variety of projects we have under third_party (eg. insisting on OWNERS, autoroll, etc.).
Is there perhaps an easy way to get the same test coverage without adding files under //third_party/? If this is the most pragmatic way to get important test coverage then I'm OK with it but you need to add a README.md file which explains why this is here and not really a new third-party dependency, and an OWNERS file - presumably just pointing at the tools/spanify OWNERS.
I missed the file location during code review.
@sergio...@google.com => Can you please move it to: `tools/clang/spanify/tests/chrome/third_party/` instead?
Thanks. I've now moved the file to tools/clang/spanify/tests/chrome/third_party/ignored.h/
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |