recursive_directory_iterator() noexcept; | (1) | (since C++17) |
recursive_directory_iterator( const recursive_directory_iterator& rhs ); | (2) | (since C++17) |
recursive_directory_iterator( recursive_directory_iterator&& rhs ) noexcept; | (3) | (since C++17) |
explicit recursive_directory_iterator( const std::filesystem::path& p ); | (4) | (since C++17) |
recursive_directory_iterator( const std::filesystem::path& p, std::filesystem::directory_options options ); | (4) | (since C++17) |
recursive_directory_iterator( const std::filesystem::path& p, std::filesystem::directory_options options, std::error_code& ec ); | (5) | (since C++17) |
recursive_directory_iterator( const std::filesystem::path& p, std::error_code& ec ); | (6) | (since C++17) |
Constructs new recursive directory iterator.
p
resolves to.The overload that does not take a std::error_code&
parameter throws filesystem::filesystem_error
on underlying OS API errors, constructed with p
as the first path argument and the OS error code as the error code argument. The overload taking a std::error_code&
parameter sets it to the OS API error code if an OS API call fails, and executes ec.clear()
if no errors occur. Any overload not marked noexcept
may throw std::bad_alloc
if memory allocation fails.
Recursive directory iterators do not follow directory symlinks by default. To enable this behavior, specify directory_options::follow_directory_symlink
among the options
option set.
The following behavior-changing defect reports were applied retroactively to previously published C++ standards.
DR | Applied to | Behavior as published | Correct behavior |
---|---|---|---|
LWG 3013 | C++17 | error_code overload marked noexcept but can allocate memory | noexcept removed |
© cppreference.com
Licensed under the Creative Commons Attribution-ShareAlike Unported License v3.0.
https://en.cppreference.com/w/cpp/filesystem/recursive_directory_iterator/recursive_directory_iterator