This is an archive of the discontinued LLVM Phabricator instance.

[clang-tidy] Extract areStatementsIdentical
ClosedPublic

Authored by PiotrZSL on Apr 22 2023, 7:43 AM.

Details

Summary

Move areStatementsIdentical from BranchCloneCheck into ASTUtils.
Add small improvments. Use it in LoopConvertUtils.

Diff Detail

Event Timeline

PiotrZSL created this revision.Apr 22 2023, 7:43 AM
Herald added a project: Restricted Project. · View Herald TranscriptApr 22 2023, 7:43 AM
Herald added a subscriber: xazax.hun. · View Herald Transcript
PiotrZSL requested review of this revision.Apr 22 2023, 7:43 AM
Herald added a project: Restricted Project. · View Herald TranscriptApr 22 2023, 7:43 AM
Herald added a subscriber: cfe-commits. · View Herald Transcript

Thanks for the refactoring, great to remove some code duplication!

As a reviewer it's not possible for me to confidently review the functional changes to areStatementsIdentical, since they don't show side by side as they are in different files. Please perform the move in one NFC patch, and apply the functional changes in a separate patch.

Thank you for your feedback regarding the code review. I understand that the review includes the removal of 35 lines and the addition of 42 lines. However, I would like to point out that the areStatementsIdentical function and the other function in question are only around 24 lines long each. Therefore, I believe that the changes made to these functions are not overly complex and can be easily reviewed as they are currently presented.

Additionally, I would like to express my concern that pushing anything through the review process currently takes up to a month. Separating the changes into two patches would only prolong this process and potentially delay the completion of this task.

If you have any questions related to the scope of the changes, I would be more than happy to answer them.

Thank you again for your time and feedback. Please let me know if you have any further concerns, and I'll do my best to address them.

carlosgalvezp accepted this revision.May 7 2023, 11:49 AM

Separating the changes into two patches would only prolong this process and potentially delay the completion of this task.

I understand the concern, but in practice it's actually the other way around. 2 small and easy to review patches are more likely to get reviewed quickly than the same patches combined into 1 big patch. The easier you make life for reviewers, the more likely they are to be willing / have time to review a patch. When I post patches, I often try and reflect about what else I can remove or make more obvious/readable to make reviewer's life easier and improve my chances of getting a quick review. I understand it's more work on the author side, but from experience I've found there's a net gain to doing it.

Anyway, the patch is indeed fairly easy to review so I'll just approve it, thank you for the contribution!

This revision is now accepted and ready to land.May 7 2023, 11:49 AM
This revision was automatically updated to reflect the committed changes.