diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-10-09 23:03:50 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-09 23:03:50 +0200 |
| commit | 866869bbbd16065656b50991e25210fbae06373b (patch) | |
| tree | 4123046ab1058f7237c38ad833b8b2149956534e /tests/coverage/branch/lazy-boolean.cov-map | |
| parent | 47344c317976626ef69942b4f6acd250079fc71a (diff) | |
| parent | 01e248ff974e310be5fb88d374cbed64aa5c4a25 (diff) | |
| download | rust-866869bbbd16065656b50991e25210fbae06373b.tar.gz rust-866869bbbd16065656b50991e25210fbae06373b.zip | |
Rollup merge of #131449 - nickrum:wasip2-net-decouple-fd, r=alexcrichton
Decouple WASIp2 sockets from WasiFd This is a follow up to #129638, decoupling WASIp2's socket implementation from WASIp1's `WasiFd` as discussed with `@alexcrichton.` Quite a few trait implementations in `std::os::fd` rely on the fact that there is an additional layer of abstraction between `Socket` and `OwnedFd`. I thus had to add a thin `WasiSocket` wrapper struct that just "forwards" to `OwnedFd`. Alternatively, I could have added a lot of conditional compilation to `std::os::fd`, which feels even worse. Since `WasiFd::sock_accept` is no longer accessible from `TcpListener` and since WASIp2 has proper support for accepting sockets through `Socket::accept`, the `std::os::wasi::net` module has been removed from WASIp2, which only contains a single `TcpListenerExt` trait with a `sock_accept` method as well as an implementation for `TcpListener`. Let me know if this is an acceptable solution.
Diffstat (limited to 'tests/coverage/branch/lazy-boolean.cov-map')
0 files changed, 0 insertions, 0 deletions
