T0b1/wasmtime
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix typo in WASI-background.md (#755)

Browse Source 
"loose" -> "lose"
"waidpid" -> "waitpid"
This commit is contained in:
Las
2020-01-01 03:29:27 +09:00
committed by Yury Delendik
parent 0e3dcaeb6e
commit 1f8921ef09
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/WASI-background.md
View File

@@ -87,9 +87,9 @@ do we want to? It'd add a bunch of complexity, inefficiency, subtle behavioral
differences, or realistically, a combination of all three. differences, or realistically, a combination of all three.
Ok, so maybe we can encourage applications to use `posix_spawn` instead. And Ok, so maybe we can encourage applications to use `posix_spawn` instead. And
some already do, but in doing so we do loose some of the value of POSIX's some already do, but in doing so we do lose some of the value of POSIX's
momentum. And even with `posix_spawn`, many applications will explicitly do momentum. And even with `posix_spawn`, many applications will explicitly do
things like `waidpid` on the resulting PID. We can make this work too, but things like `waitpid` on the resulting PID. We can make this work too, but
we should also take a moment and step back to think about IPC in general. we should also take a moment and step back to think about IPC in general.
In WebAssembly, instances can synchronously call each other, and it can be In WebAssembly, instances can synchronously call each other, and it can be