![]() LWG 3013 points out that the constructors and increment members of the directory iterators need to allocate, and therefore cannot be marked noexcept. It also points out that `is_empty` and `copy` likely need to allocate as well, and as such can also not be noexcept. This patch speculatively implements the resolution removing noexcept, because libc++ does indeed have the possibility of throwing on allocation failure. llvm-svn: 316941 |
||
---|---|---|
.. | ||
Inputs/static_test_env | ||
class.directory_entry | ||
class.directory_iterator | ||
class.file_status | ||
class.filesystem_error | ||
class.path | ||
class.rec.dir.itr | ||
fs.enum | ||
fs.error.report | ||
fs.filesystem.synopsis | ||
fs.op.funcs | ||
fs.req.macros | ||
fs.req.namespace | ||
lit.local.cfg |