This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of C++17 status.
Section: 99 [fs.op.copy_file] Status: C++17 Submitter: Eric Fiselier Opened: 2016-05-10 Last modified: 2017-07-30
View all other issues in [fs.op.copy_file].
View all issues with C++17 status.
There are a number of error cases that copy_file(from, to, ...) does not take into account. Specifically the cases where:
These error cases should be specified as such.
[2016-05 Issues Telecon]
Eric to provide wording.
[2016-05-28, Eric Fiselier provides wording]
Wed AM: Move to Tentatively Ready
This wording is relative to N4582.
Modify 99 [fs.op.copy_file] as indicated:
bool copy_file(const path& from, const path& to, copy_options options); bool copy_file(const path& from, const path& to, copy_options options, error_code& ec) noexcept;
-3- Requires: At most one constant from each copy_options option group (184.108.40.206) is present in options.-4- Effects: Report a file already exists error as specified in Error reporting (220.127.116.11) if:
- exists(to) and equivalent(from, to), or
- exists(to) and (options & (copy_options::skip_existing | copy_options::overwrite_existing | copy_options::update_existing)) == copy_options::none.