This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of TS status.
Section: 6 [filesys.ts::fs.filesystem.synopsis] Status: TS Submitter: CH-7 Opened: 2014-01-20 Last modified: 2017-07-30
Priority: Not Prioritized
View all other issues in [filesys.ts::fs.filesystem.synopsis].
View all issues with TS status.
Discussion:
Addresses: filesys.ts
Must the file_time_type hold times before 1960 and after 2050?
Specify the requirements to unspecified-trivial-clock for file_time_type.
[2014-02-10, Daniel suggests wording]
[ 2014-02-11 Issaquah: (1)Implementation-defined. See wiki notes for rationale. (2) Leave other additions in place, but insert "the" before "resolution" (3) Strike "unspecified-" from "unspecified-trivial-type" in two places. Beman to provide wording for review next meeting. ]
[2014-02-13 LWG/SG-3 Issaquah: Proposed wording accepted.]
Proposed resolution:
Modify 6 [fs.filesystem.synopsis] as indicated:
typedef chrono::time_point<unspecified-trivial-clock> file_time_type;
unspecified-trivial-clock is anunspecified type provided by the implementationimplementation-defined type that satisfies the TrivialClock requirements (C++11ISO 14882:2011 §20.12.3) and that is capable of representing and measuring file time values. Implementations should ensure that the resolution and range of file_time_type reflect the operating system dependent resolution and range of file time values.