Movatterモバイル変換

This page is a snapshot from the LWG issues list, see theLibrary Active Issues List for more information and the meaning ofC++20 status.

3026.filesystem::weakly_canonical still defined in terms ofcanonical(p, base)

Section: 31.12.13.40[fs.op.weakly.canonical]Status:C++20Submitter: Jonathan WakelyOpened: 2017-10-14Last modified: 2021-06-06

Priority:0

View all otherissues in [fs.op.weakly.canonical].

View all issues withC++20 status.

Discussion:

LWG2956⁽ⁱ⁾ fixedcanonical to no longer use a base path, butweakly_canonical should have beenchanged too:

Effects: Usingstatus(p) orstatus(p, ec), respectively, to determineexistence, return a path composed byoperator/= from the result of callingcanonical() withoutabase argument and with a […]

Sincecanonical doesn't accept abase argument, it doesn't make senseto talk about calling it without one.

[2017-10-16 Moved to Tentatively Ready after 5 positive votes on c++std-lib.]

[2018-3-17 Adopted in Jacksonville]

Proposed resolution:

This wording is relative toN4687.

1. Change [fs.op.weakly_canonical] as indicated:

   path weakly_canonical(const path& p);path weakly_canonical(const path& p, error_code& ec);

   -1-Returns: […]

   -2-Effects: Usingstatus(p) orstatus(p, ec), respectively, to determine existence, return a pathcomposed byoperator/= from the result of callingcanonical()without abase argument andwith a path argument composed of the leading elements ofp that exist, if any, followed by the elements ofpthat do not exist, if any. For the first form,canonical() is called without anerror_code argument.For the second form,canonical() is called with ec as anerror_code argument, andpath() is returnedat the first error occurrence, if any.

   […]