diff options
| author | Alex Langford <alangford@apple.com> | 2023-08-28 11:59:09 -0700 |
|---|---|---|
| committer | Alex Langford <alangford@apple.com> | 2023-09-14 10:19:53 -0700 |
| commit | 2f377c5bd713e9ee72faa6a99088bb81358059e3 (patch) | |
| tree | a84aa091dbba6529da438066f4064afb1a6f1b23 /clang/lib/Analysis/FlowSensitive/DataflowAnalysisContext.cpp | |
| parent | 8c2da6bb7f48d2dded1c0a2b2c43217f90011d42 (diff) | |
| download | llvm-2f377c5bd713e9ee72faa6a99088bb81358059e3.zip llvm-2f377c5bd713e9ee72faa6a99088bb81358059e3.tar.gz llvm-2f377c5bd713e9ee72faa6a99088bb81358059e3.tar.bz2 | |
[lldb][NFCI] Remove use of ConstString from UnixSignals
The majority of UnixSignals strings are static in the sense that they do
not change. The overwhelming majority of these strings are string
literals. Using ConstString to manage their lifetime does not make
sense. The only exception to this is one of the subclasses of
UnixSignals, for which I have created a StringSet local to that file
which will guarantee the lifetimes of these StringRefs.
As for the other benefits of ConstString, string uniqueness is not a
concern (as many of them are already string literals) and comparing
signal names and aliases should not be a hot path.
Differential Revision: https://reviews.llvm.org/D159011
Diffstat (limited to 'clang/lib/Analysis/FlowSensitive/DataflowAnalysisContext.cpp')
0 files changed, 0 insertions, 0 deletions