aboutsummaryrefslogtreecommitdiff
path: root/clang/unittests/Interpreter/InterpreterTest.cpp
diff options
context:
space:
mode:
authorPete Lawrence <plawrence@apple.com>2024-01-18 10:04:26 -1000
committerGitHub <noreply@github.com>2024-01-18 12:04:26 -0800
commitc82b7fddfcbd6adfae4faf324a453fb8652efa91 (patch)
tree54cf5292af1f1e2f83ae640a3472ec88ea3944f9 /clang/unittests/Interpreter/InterpreterTest.cpp
parent99cae9a44fca4cfbd6ee82f196051cbdf6571fa1 (diff)
downloadllvm-c82b7fddfcbd6adfae4faf324a453fb8652efa91.zip
llvm-c82b7fddfcbd6adfae4faf324a453fb8652efa91.tar.gz
llvm-c82b7fddfcbd6adfae4faf324a453fb8652efa91.tar.bz2
[lldb] Remove redundant severity substring within a diagnostic message. (#76111)
For example, the following message has the severity string "error: " twice. > "error: <EXPR>:3:1: error: cannot find 'bogus' in scope This method already appends the severity string in the beginning, but with this fix, it also removes a secondary instance, if applicable. Note that this change only removes the *first* redundant substring. I considered putting the removal logic in a loop, but I decided that if something is generating more than one redundant severity substring, then that's a problem the message's source should probably fix. rdar://114203423
Diffstat (limited to 'clang/unittests/Interpreter/InterpreterTest.cpp')
0 files changed, 0 insertions, 0 deletions