feedc0de/date
1
0
Fork 0
forked from HowardHinnant/date
Code Pull Requests Activity

Embellish issue 2.

Browse Source
This commit is contained in:
Howard Hinnant
2016-10-15 21:15:24 -04:00
parent dd209e205e
commit 41657bc50e
1 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
d0355r1.html
View File

@@ -606,9 +606,9 @@ a way that it is trivial to remove this functionality.
<li> <li>
<p> <p>
Currently this library passes <code>time_zone</code>s around with Currently this library passes <code>time_zone</code>s around with
<code>const time_zone*</code>. Each <code>time_zone</code> is a non-copyable singleton <code>const time_zone*</code>. Each <code>time_zone</code> is a non-copyable
in the application (much like a <code>type_info</code>). Passing them around by pointers <code>const</code> singleton in the application (much like a
allows syntax such as: <code>type_info</code>). Passing them around by pointers allows syntax such as:
</p> </p>
<blockquote><pre> <blockquote><pre>
auto tz = current_zone(); auto tz = current_zone();
@@ -633,6 +633,13 @@ the following work no matter what with this syntax:
<blockquote><pre> <blockquote><pre>
cout &lt;&lt; make_zoned(current_zone(), system_clock::now()) &lt;&lt; '\n'; cout &lt;&lt; make_zoned(current_zone(), system_clock::now()) &lt;&lt; '\n';
</pre></blockquote> </pre></blockquote>
<p>
We simply need to decide if the default style guide for passing <code>time_zone</code>s
around is <code>const time_zone*</code> or <code>const time_zone&amp;</code>. And yes,
it is ok for a client to have a <code>const time_zone*</code> which equals
<code>nullptr</code>. And no, the library never provides a <code>const time_zone*</code>
which is equal to <code>nullptr</code>.
</p>
</li> </li>
</ol> </ol>