This is an archive of the discontinued LLVM Phabricator instance.

[libc++][NFC] Disable clang-tidy checks
ClosedPublic

Authored by philnik on Dec 2 2021, 12:12 PM.

Details

Reviewers
ldionne
Quuxplusone
Group Reviewers
Restricted Project
Commits
rGf50be8eb0a12: [libc++][NFC] Disable clang-tidy checks
Summary

Disable clang-tidy checks as discussed in D114915

Diff Detail

Event Timeline

philnik requested review of this revision.Dec 2 2021, 12:12 PM
philnik created this revision.
Herald added a project: Restricted Project. · View Herald TranscriptDec 2 2021, 12:12 PM
Herald added a reviewer: Restricted Project. · View Herald Transcript
cjdb added a subscriber: cjdb.Dec 2 2021, 12:40 PM

Why is llvm-else-after-return disabled? That's a pretty important readability improvement. What about llvm-header-guard?

ldionne added a comment.EditedDec 2 2021, 12:54 PM

Why is llvm-else-after-return disabled? That's a pretty important readability improvement. What about llvm-header-guard?

IIUC llvm-else-after-return is the thing that tries to remove any else after an if that contains a return? IMO that's not a readability improvement at all, at least not in the places where it modified the code in D114915.

You are right, llvm-else-after-return is the check for that.

cjdb added a comment.Dec 2 2021, 2:43 PM

Why is llvm-else-after-return disabled? That's a pretty important readability improvement. What about llvm-header-guard?

IIUC llvm-else-after-return is the thing that tries to remove any else after an if that contains a return? IMO that's not a readability improvement at all, at least not in the places where it modified the code in D114915.

I found a lot of the changes to improve readability, but the __libcpp_is_constant_evaluated ones were dubious and I can see why we should disable it for the time being.

ldionne accepted this revision.Dec 3 2021, 4:13 AM
This revision is now accepted and ready to land.Dec 3 2021, 4:13 AM
This revision was automatically updated to reflect the committed changes.