Skip to content

Add wording for LWG 4454 #556

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jwakely merged 1 commit into from
Mar 6, 2026
Merged

Add wording for LWG 4454 #556

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions xml/issue4454.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,10 +23,20 @@ are not valid in unevaluated contexts, unless we are certain that the
new `assert` requirements can be implemented without such tricks using
unevaluated contexts. "Ill-formed; no diagnostic required" seems appropriate.
</p>
<note>2026-03-06 Tim provides wording</note>
</discussion>

<resolution>
<p>
<li><p>Modify <sref ref="[assertions.assert]"/> as indicated:</p>
<blockquote>
<p>
-3- If `__VA_ARGS__` does not expand to <del>an</del><ins>a well-formed</ins> <i>assignment-expression</i>, the program is ill-formed.
<ins>If such an <i>assignment-expression</i> is ill-formed when treated as an unevaluated operand (<sref ref="[expr.await]"/>, <sref ref="[expr.yield]"/>),
the program is ill-formed, no diagnostic required.</ins>
</p>
</blockquote>
</li>
</p>
</resolution>

Expand Down