Fix constexpr execution of if statement with static_assert declaration substatement #1312
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stop null dereference in ExecIf when thenClauseExec is null. This happens with throw declaration in thenClause, and ExecIf already allows for null in elseClauseExec so this is a bit more consistent.
Null thenClauseExec can be from encountered valid static_assert declaration, handle it during constexpr execution as new special problem type STATIC_ASSERT_FAILED.
Fix these and add unit test.