<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>A new LWG issue was filed for this question today:<br>
- <a class="moz-txt-link-freetext" href="https://cplusplus.github.io/LWG/issue3314">https://cplusplus.github.io/LWG/issue3314</a></p>
<p>This issue concerns the ostream inserters added for <tt>std::chrono::duration</tt>
in C++20 and what the intended behavior is for a duration when <tt>period::type</tt>
is <tt>micro</tt>.</p>
<p><a moz-do-not-send="true"
href="http://eel.is/c++draft/time.duration.io#4">[time.duration.io]p4</a>
states:<br>
</p>
<p>
<blockquote type="cite">
<p>If <tt><span class="texttt">Period<span class="operator">::</span>type</span></tt>
is <tt><span class="texttt">micro</span></tt>,
but the character U+00B5 cannot be represented in
the encoding used for <tt><span class="texttt">charT</span></tt>,
the unit suffix <tt><span class="texttt"><span
class="literal">"us"</span></span></tt> is used instead
of <tt><span class="texttt"><span class="literal">"μs"</span></span></tt>.</p>
</blockquote>
</p>
<p>The question is with regard to which one of the encodings used
for <tt>charT</tt> is referred to here; the compile-time
execution character set or the run-time locale dependent native
character set?<br>
</p>
<p>The proposed resolution specifies that the compile-time execution
character set is the intended one. My expectation is that this
aligns with existing implementations, but I haven't checked.</p>
<p>Tom.<br>
</p>
</body>
</html>