This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of New status.
Section: 184.108.40.206 [fs.enum.path.format], 99 [fs.class.directory_iterator], 220.127.116.11 [fs.op.copy] Status: New Submitter: Thomas Köppe Opened: 2017-03-14 Last modified: 2018-01-22
View all issues with New status.
During the application of P0430R2, we came across several terms that seem insufficiently clear and lacking proper definitions.We would like clarification on what those terms mean, and we would welcome wording suggestions, or alternatively a verbose explanation and dispensation to change the presentation editorially. The items in question are:
What does it mean to 'always interpret [the character sequence] in the same way'? ([fs.enum.path.format], which is [path.format] in the paper)
What is a "directory-like" file type? ([fs.class.directory_iterator])
What is an "implementation-defined file type"? (e.g. [fs.op.copy])
[2017-07 Toronto Wed Issue Prioritization]
[2018-01-16, Jonathan comments]
In 18.104.22.168 [fs.enum.path.format] "always interpreted in the same way" means irrespective of the path::format value, or the content of the string. Maybe add ", rather than depending on the path::format value or the content of the character sequence".In 99 [fs.class.directory_iterator] an "implementation-defined directory-like file type" is an implementation-defined file type (see 99 [fs.enum.file_type] and Table 115) that is treated like a directory by the special rules that the OS has for non-regular files (see 22.214.171.124 [fs.path.generic]). In 126.96.36.199 [fs.op.copy], an "implementation-defined file type" is exactly that, see 99 [fs.enum.file_type] and Table 115 again. I don't see what isn't clear about that. Maybe add a cross-reference to 99 [fs.enum.file_type].