Title
[filesys.ts] [PDTS] path and directory_entry move ctors should not be noexcept
Status
open
Section
[path.construct] [class.directory_entry]
Submitter
Stephan T. Lavavej

Created on 2014-02-03.00:00:00 last changed 81 months ago

Messages

Date: 2016-01-28.01:00:35

Proposed resolution:

Change 8 Class path [class.path]:
path() noexcept;
Change 8.4.1 path constructors [path.construct]:
path() noexcept;
Change 12 Class directory_entry [class.directory_entry]:
directory_entry() noexcept = default;
Date: 2016-01-28.01:00:35

[ 19 Jun 2014 LWG revises P/R to stay consistent with LWG issues. ]

Date: 2016-02-11.02:13:37

[ 21 May 2014 Beman Dawes provides wording. See 2319 for rationale. ]

Date: 2016-01-28.01:00:35

[ Beman Dawes 2014-02-27 ]

Issues 2637, 2638, 2641, and 2649 are concerned with signatures which should or should not be noexcept. I will provide unified proposed wording for these issues, possibly in a separate paper.

Date: 2016-01-31.20:31:05

Addresses: filesys.ts

path's move ctor is marked noexcept, but it contains a basic_string. Similarly, directory_entry's move ctor is marked noexcept, but it contains a path. This is affected by LWG 2319 "basic_string's move constructor should not be noexcept".

History
Date User Action Args
2017-07-30 20:10:41adminsetstatus: wp -> open
2016-01-28 01:00:35adminsetmessages: + msg7870
2016-01-28 01:00:35adminsetmessages: + msg7869
2016-01-28 01:00:35adminsetmessages: + msg7868
2016-01-28 01:00:35adminsetmessages: + msg7867
2014-02-03 00:00:00admincreate