Created on 2016-05-28.00:00:00 last changed 90 months ago
Proposed resolution:
This wording is relative to N4582.
Change [fs.filesystem.syn] as indicated:
namespace std::filesystem { […] void permissions(const path& p, perms prms); void permissions(const path& p, perms prms, error_code& ec)noexcept; […] }
Change [fs.op.permissions] as indicated:
void permissions(const path& p, perms prms); void permissions(const path& p, perms prms, error_code& ec)noexcept;-1- Requires: !((prms & perms::add_perms) != perms::none && (prms & perms::remove_perms) != perms::none).
[ 2016-06 Oulu ]
Moved to P0/Ready during issues prioritization.
Friday: status to Immediate
Currently the signatures for permissions are:
void permissions(const path& p, perms prms); void permissions(const path& p, perms prms, error_code& ec) noexcept;
However both overloads have a narrow contract since due to the requires clause:
Requires: !((prms & perms::add_perms) != perms::none && (prms & perms::remove_perms) != perms::none).
For this reason I believe the second overload of permissions should not be marked noexcept.
History | |||
---|---|---|---|
Date | User | Action | Args |
2017-07-30 20:15:43 | admin | set | status: wp -> c++17 |
2016-06-28 13:14:43 | admin | set | status: immediate -> wp |
2016-06-27 16:42:33 | admin | set | status: ready -> immediate |
2016-06-21 17:05:07 | admin | set | messages: + msg8190 |
2016-06-20 16:35:58 | admin | set | status: new -> ready |
2016-06-05 15:19:54 | admin | set | messages: + msg8157 |
2016-05-28 00:00:00 | admin | create |