Skip to content

Commit 188f80b

Browse files
committed
Add P/R to 3678
1 parent 7f2ae82 commit 188f80b

File tree

1 file changed

+42
-0
lines changed

1 file changed

+42
-0
lines changed

xml/issue3678.xml

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,51 @@ and <tt>constexpr</tt>-ness should be left unspecified.
2727
Set priority to 4 after reflector poll.
2828
</p>
2929

30+
<note>2025-03-18; Jonathan provides wording</note>
31+
<p>
32+
I don't think it matters whether they are trivial or constexpr, because they
33+
cannot be used. Users only have access to `const time_zone` lvalues via
34+
`locate_zone` and the `tzdb::zones` container.
35+
The move constructor and move assignment operator only need to exist so that
36+
the implementation can populate that container.
37+
</p>
38+
3039
</discussion>
3140

3241
<resolution>
42+
<p>
43+
This wording is relative to <paper num="N5001"/>.
44+
</p>
45+
46+
<ol>
47+
<li><p>Modify <sref ref="[time.zone.overview]"/> as indicated:</p>
48+
<blockquote><pre><code>
49+
namespace std::chrono {
50+
class time_zone {
51+
<ins>time_zone(<i>unspecified</i>);</ins>
52+
public:
53+
time_zone(time_zone&amp;&amp;) = default;
54+
time_zone&amp; operator=(time_zone&amp;&amp;) = default;
55+
56+
<del><i>// unspecified additional constructors</i></del>
57+
58+
<i>[...]</i>
59+
};
60+
}</code></pre></blockquote>
61+
<p>-1-
62+
A `time_zone` represents all time zone transitions for a specific geographic
63+
area.
64+
`time_zone` construction is unspecified, and performed
65+
<ins>only</ins>
66+
as part of database initialization.
67+
</p>
68+
<p>
69+
[<i>Note 1</i>:
70+
`const time_zone` objects can be accessed via functions such as `locate_zone`.
71+
&mdash; <i>end note</i>]
72+
</p>
73+
</li>
74+
</ol>
3375
</resolution>
3476

3577
</issue>

0 commit comments

Comments
 (0)