Piotr Osiewicz 529aae6fc3 wasi/fs: Improve stopping condition for <ReadDir as Iterator>::next ... When upgrading [Zed](https://github.com/zed-industries/zed/pull/19349) to Rust 1.82 I've encountered a test failure in our test suite. Specifically, one of our extension tests started hanging. I've tracked it down to a call to std::fs::remove_dir_all not returning when an extension is compiled with Rust 1.82 Our extension system uses WASM components, thus I've looked at the diff between 1.81 and 1.82 with respect to WASI and found 736f773844 As it turned out, calling remove_dir_all from extension returned io::ErrorKind::NotFound in 1.81; the underlying issue is that the ReadDir iterator never actually terminates iteration, however since it loops around, with 1.81 we'd come across an entry second time and fail to remove it, since it would've been removed previously. With 1.82 and 736f773844 it is no longer the case, thus we're seeing the hang. This commit makes ReadDir::next adhere to readdir contract, namely it will no longer call readdir once the returned # of bytes is smaller than the size of a passed-in buffer. Previously we'd only terminate the loop if readdir returned 0.		2024-11-18 19:19:14 +01:00
..
benches	Reformat use declarations.	2024-07-29 08:26:52 +10:00
src	wasi/fs: Improve stopping condition for <ReadDir as Iterator>::next	2024-11-18 19:19:14 +01:00
tests	Avoid shadowing user provided types or type aliases in thread_local!	2024-10-18 10:27:41 +08:00
build.rs	Enable f128 tests on all non-buggy platforms 🎉	2024-11-03 19:33:04 -06:00
Cargo.toml	unpin and update memchr	2024-11-07 02:09:39 +01:00