main

文件	最后提交记录	最后更新时间
CFCBundle.cpp	[lldb] Replace default bodies of special member functions with = default; Replace default bodies of special member functions with = default; $ run-clang-tidy.py -header-filter='lldb' -checks='-*,modernize-use-equals-default' -fix , https://clang.llvm.org/extra/clang-tidy/checks/modernize-use-equals-default.html Differential revision: https://reviews.llvm.org/D104041	5 年前
CFCBundle.h	[lldb] Fix modernize-use-override warnings (NFC) Fix modernize-use-override warnings. Because this check is listed in LLDB's top level .clang-tidy configuration, the check is enabled by default and the resulting warnings show up in my editor. I've audited the modified lines. This is not a blind change.	4 年前
CFCData.cpp	[lldb] Replace deprecated CFPropertyListWriteToStream (NFC) Replace CFPropertyListWriteToStream with its recommended replacement, CFPropertyListWrite. Differential Revision: https://reviews.llvm.org/D147249	3 年前
CFCData.h	[lldb] Fix modernize-use-override warnings (NFC) Fix modernize-use-override warnings. Because this check is listed in LLDB's top level .clang-tidy configuration, the check is enabled by default and the resulting warnings show up in my editor. I've audited the modified lines. This is not a blind change.	4 年前
CFCMutableArray.cpp	[LLDB] Applying clang-tidy modernize-use-equals-default over LLDB Applied modernize-use-equals-default clang-tidy check over LLDB. This check is already present in the lldb/.clang-tidy config. Differential Revision: https://reviews.llvm.org/D121844	4 年前
CFCMutableArray.h	[lldb] Fix modernize-use-override warnings (NFC) Fix modernize-use-override warnings. Because this check is listed in LLDB's top level .clang-tidy configuration, the check is enabled by default and the resulting warnings show up in my editor. I've audited the modified lines. This is not a blind change.	4 年前
CFCMutableDictionary.cpp	[LLDB] Applying clang-tidy modernize-use-equals-default over LLDB Applied modernize-use-equals-default clang-tidy check over LLDB. This check is already present in the lldb/.clang-tidy config. Differential Revision: https://reviews.llvm.org/D121844	4 年前
CFCMutableDictionary.h	[lldb] Fix modernize-use-override warnings (NFC) Fix modernize-use-override warnings. Because this check is listed in LLDB's top level .clang-tidy configuration, the check is enabled by default and the resulting warnings show up in my editor. I've audited the modified lines. This is not a blind change.	4 年前
CFCMutableSet.cpp	[LLDB] Applying clang-tidy modernize-use-equals-default over LLDB Applied modernize-use-equals-default clang-tidy check over LLDB. This check is already present in the lldb/.clang-tidy config. Differential Revision: https://reviews.llvm.org/D121844	4 年前
CFCMutableSet.h	[lldb] Fix modernize-use-override warnings (NFC) Fix modernize-use-override warnings. Because this check is listed in LLDB's top level .clang-tidy configuration, the check is enabled by default and the resulting warnings show up in my editor. I've audited the modified lines. This is not a blind change.	4 年前
CFCReleaser.h	[lldb][NFCI] Remove use of ifdef __cpluplus where unneeded Just about every file in the lldb project is built with C++ enabled. Unless I've missed something, these macro guards don't really accomplish very much. Differential Revision: https://reviews.llvm.org/D157538	2 年前
CFCString.cpp	[LLDB] Applying clang-tidy modernize-use-equals-default over LLDB Applied modernize-use-equals-default clang-tidy check over LLDB. This check is already present in the lldb/.clang-tidy config. Differential Revision: https://reviews.llvm.org/D121844	4 年前
CFCString.h	[lldb] Fix modernize-use-override warnings (NFC) Fix modernize-use-override warnings. Because this check is listed in LLDB's top level .clang-tidy configuration, the check is enabled by default and the resulting warnings show up in my editor. I've audited the modified lines. This is not a blind change.	4 年前
CoreFoundationCPP.h	[NFC] Remove ASCII lines from comments A lot of comments in LLDB are surrounded by an ASCII line to delimit the begging and end of the comment. Its use is not really consistent across the code base, sometimes the lines are longer, sometimes they are shorter and sometimes they are omitted. Furthermore, it looks kind of weird with the 80 column limit, where the comment actually extends past the line, but not by much. Furthermore, when /// is used for Doxygen comments, it looks particularly odd. And when // is used, it incorrectly gives the impression that it's actually a Doxygen comment. I assume these lines were added to improve distinguishing between comments and code. However, given that todays editors and IDEs do a great job at highlighting comments, I think it's worth to drop this for the sake of consistency. The alternative is fixing all the inconsistencies, which would create a lot more churn. Differential revision: https://reviews.llvm.org/D60508 llvm-svn: 358135	7 年前