diff options
| author | Guillaume Gomez <guillaume1.gomez@gmail.com> | 2025-05-01 22:27:22 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-05-01 22:27:22 +0200 |
| commit | 5170e21cb915cb2c4d2eec57cc56527131e93699 (patch) | |
| tree | b87daa38645e513c7140ffeb0079d4473d24b8cb /tests/rustdoc/source-code-pages/version-separator-without-source.rs | |
| parent | 5a25a7a020afd5bb9f9eaaf3a4e5622c26a9276e (diff) | |
| parent | 3a372e39ca54339925bf01ead93b3c1dc01078d2 (diff) | |
| download | rust-5170e21cb915cb2c4d2eec57cc56527131e93699.tar.gz rust-5170e21cb915cb2c4d2eec57cc56527131e93699.zip | |
Rollup merge of #140062 - xizheyin:issue-139958, r=workingjubilee
std: mention `remove_dir_all` can emit `DirectoryNotEmpty` when concurrently written into Closes #139958 The current documentation for `std::fs::remove_dir_all` function does not explicitly mention the error types that may be returned in concurrent scenarios. Specifically, when one thread attempts to remove a directory tree while another thread simultaneously writes files to that directory, the function may return an `io::ErrorKind::DirectoryNotEmpty` error, but this behavior is not clearly mentioned in the current documentation. r? libs
Diffstat (limited to 'tests/rustdoc/source-code-pages/version-separator-without-source.rs')
0 files changed, 0 insertions, 0 deletions
