Issue 2629: [filesys.ts] [PDTS] Unclear semantics of read_symlink on error

Title: [filesys.ts] [PDTS] Unclear semantics of read_symlink on error
Status: open
Section: [fs.op.read_symlink]
Submitter: GB-16

Created on 2014-01-20.00:00:00 last changed 90 months ago

Messages

Date: 2016-01-28.01:00:35

Proposed resolution:

Change 15.27 [fs.op.read_symlink]:

Returns: If p resolves to a symbolic link, a path object containing the contents of that symbolic link. ~~Otherwise path().~~ The signature with argument ec returns path() if an error occurs.

Throws: As specified in Error reporting. [Note: It is an error if p does not resolve to a symbolic link. — end note]

msg7791 (view)

Date: 2014-02-13.00:00:00

[ 2014-02-13 LWG/SG-3 Issaquah: Proposed wording accepted. ]

msg7790 (view)

Date: 2014-02-15.00:00:00

[ 2014-02-09, Beman Dawes provides wording ]

msg7789 (view)

Date: 2016-01-31.20:31:05

Addresses: filesys.ts

Unclear semantics of read_symlink on error: 15.27 [fs.op.read_symlink] has: Returns: If p resolves to a symbolic link, a path object containing the contents of that symbolic link. Otherwise path(). and also [Note: It is an error if p does not resolve to a symbolic link. -- end note]

I do not believe path() can be a valid return for the overload not taking error_code.

Strike "Otherwise path()."

History
Date	User	Action	Args
2017-07-30 20:10:41	admin	set	status: wp -> open
2016-01-28 01:00:35	admin	set	messages: + msg7792
2016-01-28 01:00:35	admin	set	messages: + msg7791
2016-01-28 01:00:35	admin	set	messages: + msg7790
2014-01-20 00:00:00	admin	create