|
1 | 1 | @since(version = 0.2.0)
|
2 | 2 | interface tcp {
|
3 | 3 | @since(version = 0.2.0)
|
4 |
| - use wasi:io/streams@0.2.2.{input-stream, output-stream}; |
| 4 | + use wasi:io/streams@0.2.3.{input-stream, output-stream}; |
5 | 5 | @since(version = 0.2.0)
|
6 |
| - use wasi:io/poll@0.2.2.{pollable}; |
| 6 | + use wasi:io/poll@0.2.3.{pollable}; |
7 | 7 | @since(version = 0.2.0)
|
8 |
| - use wasi:clocks/monotonic-clock@0.2.2.{duration}; |
| 8 | + use wasi:clocks/monotonic-clock@0.2.3.{duration}; |
9 | 9 | @since(version = 0.2.0)
|
10 | 10 | use network.{network, error-code, ip-socket-address, ip-address-family};
|
11 | 11 |
|
@@ -66,7 +66,7 @@ interface tcp {
|
66 | 66 | /// - `not-in-progress`: A `bind` operation is not in progress.
|
67 | 67 | /// - `would-block`: Can't finish the operation, it is still in progress. (EWOULDBLOCK, EAGAIN)
|
68 | 68 | ///
|
69 |
| - /// # Implementers note |
| 69 | + /// # Implementors note |
70 | 70 | /// When binding to a non-zero port, this bind operation shouldn't be affected by the TIME_WAIT
|
71 | 71 | /// state of a recently closed socket on the same local address. In practice this means that the SO_REUSEADDR
|
72 | 72 | /// socket option should be set implicitly on all platforms, except on Windows where this is the default behavior
|
@@ -115,7 +115,7 @@ interface tcp {
|
115 | 115 | /// - `not-in-progress`: A connect operation is not in progress.
|
116 | 116 | /// - `would-block`: Can't finish the operation, it is still in progress. (EWOULDBLOCK, EAGAIN)
|
117 | 117 | ///
|
118 |
| - /// # Implementers note |
| 118 | + /// # Implementors note |
119 | 119 | /// The POSIX equivalent of `start-connect` is the regular `connect` syscall.
|
120 | 120 | /// Because all WASI sockets are non-blocking this is expected to return
|
121 | 121 | /// EINPROGRESS, which should be translated to `ok()` in WASI.
|
@@ -148,7 +148,7 @@ interface tcp {
|
148 | 148 | /// - `not-in-progress`: A listen operation is not in progress.
|
149 | 149 | /// - `would-block`: Can't finish the operation, it is still in progress. (EWOULDBLOCK, EAGAIN)
|
150 | 150 | ///
|
151 |
| - /// # Implementers note |
| 151 | + /// # Implementors note |
152 | 152 | /// Unlike in POSIX, in WASI the listen operation is async. This enables
|
153 | 153 | /// interactive WASI hosts to inject permission prompts. Runtimes that
|
154 | 154 | /// don't want to make use of this ability can simply call the native
|
|
0 commit comments