summaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptedProcessPythonInterface.cpp
diff options
context:
space:
mode:
authorMuhammad Usman Shahid <codesbyusman@gmail.com>2022-07-21 06:32:54 -0700
committerErich Keane <erich.keane@intel.com>2022-07-21 06:34:14 -0700
commit6542cb55a3eb115b1c3592514590a19987ffc498 (patch)
tree3d63386ea2363dcdf473c8453c096c910bbb2885 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptedProcessPythonInterface.cpp
parentbc33c2fa0c2a68a0431df0d825cc6df99a1883db (diff)
Rewording the "static_assert" to static assertion
This patch is basically the rewording of the static assert statement's output(error) on screen after failing. Failing a _Static_assert in C should not report that static_assert failed. It’d probably be better to reword the diagnostic to be more like GCC and say “static assertion” failed in both C and C++. consider a c file having code _Static_assert(0, "oh no!"); In clang the output is like: <source>:1:1: error: static_assert failed: oh no! _Static_assert(0, "oh no!"); ^ ~ 1 error generated. Compiler returned: 1 Thus here the "static_assert" is not much good, it will be better to reword it to the "static assertion failed" to more generic. as the gcc prints as: <source>:1:1: error: static assertion failed: "oh no!" 1 | _Static_assert(0, "oh no!"); | ^~~~~~~~~~~~~~ Compiler returned: 1 The above can also be seen here. This patch is about rewording the static_assert to static assertion. Differential Revision: https://reviews.llvm.org/D129048
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptedProcessPythonInterface.cpp')
0 files changed, 0 insertions, 0 deletions