diff options
| author | Aaron Ballman <aaron@aaronballman.com> | 2022-01-18 11:57:59 -0500 |
|---|---|---|
| committer | Aaron Ballman <aaron@aaronballman.com> | 2022-01-18 11:59:08 -0500 |
| commit | fa596fb0779ae9029edbcff80ff95e9d1a816206 (patch) | |
| tree | 833187f72a3f546cb99c5caa626c629084d38313 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptedPythonInterface.h | |
| parent | 5c36ee8d57fa702d8dc4ee9349978bff575a9465 (diff) | |
Fix a failed assertion on an invalid typename requirement
The parsing code for a typename requirement currently asserts when
given something which is not a valid type-requirement
(http://eel.is/c++draft/expr.prim.req.type#nt:type-requirement). This
removes the assertion to continue on to the proper diagnostic.
This resolves PR53057.
Note that in that PR, it is using _BitInt(N) as a dependent type name.
This patch does not attempt to support that as it is not clear that is
a valid type requirement (it does not match the grammar production for
one). The workaround in the PR, however, is definitely valid and works
as expected.
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptedPythonInterface.h')
0 files changed, 0 insertions, 0 deletions