<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [clang-cl] MSVC to add /std:c++20 soon"
href="https://bugs.llvm.org/show_bug.cgi?id=50465">50465</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[clang-cl] MSVC to add /std:c++20 soon
</td>
</tr>
<tr>
<th>Product</th>
<td>clang
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>PC
</td>
</tr>
<tr>
<th>OS</th>
<td>Windows NT
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Driver
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedclangbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>Casey@Carter.net
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org, neeilans@live.com, richard-llvm@metafoo.co.uk
</td>
</tr></table>
<p>
<div>
<pre>MSVC will be adding the `/std:c++20` option in our 16.11 release. More
precisely, you could say we'll rename the existing `/std:c++latest` to
`/std:c++20` (which defines `_MSVC_LANG` to C++20's __cplusplus value of
`202002L`) and then add a new `/std:c++latest` option which defines
`_MSVC_LANG` to `202004L`. (I have no idea how the compiler team chose
`202004L`, but I suppose it doesn't matter as long as the value is `> 202002L`.
Perhaps <a href="https://xkcd.com/221/">https://xkcd.com/221/</a>?)
clang-cl should be updated to have the same behavior in the next release.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>