From 638b81d23db43849d606e6fb005f0918f6e95ed1 Mon Sep 17 00:00:00 2001 From: Dave Bakker Date: Sat, 10 Jan 2026 11:34:23 +0100 Subject: [PATCH] Clarify the implicit bind behavior observed on Windows. --- proposals/sockets/wit-0.3.0-draft/types.wit | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/proposals/sockets/wit-0.3.0-draft/types.wit b/proposals/sockets/wit-0.3.0-draft/types.wit index 02b1bb7e..be2a381c 100644 --- a/proposals/sockets/wit-0.3.0-draft/types.wit +++ b/proposals/sockets/wit-0.3.0-draft/types.wit @@ -276,6 +276,12 @@ interface types { /// In either case, the stream returned by this `listen` method remains /// operational. /// + /// WASI requires `listen` to perform an implicit bind if the socket + /// has not already been bound. Not all platforms (notably Windows) + /// exhibit this behavior out of the box. On platforms that require it, + /// the WASI implementation can emulate this behavior by performing + /// the bind itself if the guest hasn't already done so. + /// /// # References /// - /// -