en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wasi/src/cli/stdout.rs#d73bd632 Migrate `wasmtime-wasi` to `wasmtime::error` (#12294)* Migrate wiggle and wiggle generate to `wasmtime::error`* Fix testing `wiggle` and `wiggle-test` in isolationWhen doing plain old `cargo test -p wiggle` (or `wiggle-test`) the test wouldfail due to linking errors because Wasmtime's `std` cargo feature (and maybeothers) wasn't being enabled. The crate's tests would pass when run as part ofthe whole workspace, however, because of cargo feature resolution and othercrates that enabled the necessary features, which is why CI is green.* Remove direct anyhow dependency in wiggle-test* Migrate wasi-nn to `wasmtime::error`* Migrate wasi-keyvalue to `wasmtime::error`* Migrate wasi-io to `wasmtime::error`* Migrate wasi-http to `wasmtime::error`* Migrate wasi-config to `wasmtime::error`* Migrate wasi-common to `wastime::error`This is another interesting one because wasi-common is used internally toWasmtime but also by other projects. Therefore, rather than using`wastime::error::*` and making `wasmtime` a hard dependency, we use just`wasmtime_environ::error`.* cargo fmt* Migrate wasmtime-wasi to `wasmtime::error` List of files: /wasmtime-44.0.1/crates/wasi/src/cli/stdout.rs Fri, 09 Jan 2026 17:28:46 +0000 Nick Fitzgerald <fitzgen@gmail.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wasi/src/cli/stdout.rs#2fd0c7bf wasip3: Update std{out,err} implementation (#11618)* wasip3: Update std{out,err} implementationMatch the WASIp2 stdio implementation and "lie" about stdio actuallybeing async. Instead of using Tokio's primitives use the `std::io`primitives which will block the current program while the output isproduced. This matches WASIp2 semantics and we always have the option ofmaking this more async in the future (or even have it as a runtimeflag). This avoids the need to call `poll_flush` in stdiounconditionally in the `wasi:cli` implementation which didn't feel quiteright.* One fewer run for WindowsIt's got a shorter command line length limit List of files: /wasmtime-44.0.1/crates/wasi/src/cli/stdout.rs Fri, 05 Sep 2025 17:16:23 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wasi/src/cli/stdout.rs#e6a662b3 Share stdio implementations in WASIp{2,3} (#11368)* Share stdio implementations in WASIp{2,3}This commit is a refactoring of the`wasmtime_wasi::{cli,p2::stdio,p3::cli}` modules to share more code. Thegeneric trait object that represents stdio now has the ability toacquire either a p2 stream or an async-based stream. The acquisition ofp2 has a default implementation so in the future this can be primarily`Async{Read,Write}`-based.Many trait implementations and types and such were all consolidatedtogether into the `wasmtime_wasi::cli` module. One-off implementationsin p2/p3 are now shared in one location and `WasiCtxBuilder` no longerneeds any generics for different stdio streams.Functionally this necessitated the addition of `Async{Read,Write}`implementations for some "base" implementations of stdio primitives.Implementations were mostly trivial except for a few adapters which weresignificantly more complicated, namely the `Async{Read,Write}Stream`adapter which converts a single `Async{Read,Write}` into the stdio of acomponent.Finally the stdin implementation for p3 was refactored to avoid use of`tokio::io::stdin()` which generally isn't safe to use. It's replacedwith a custom `AsyncRead` using the worker thread implementation we havein the crate already.Eventually I hope to remove the distinction between `p{2,3}::WasiCtx`and have these be the same type. This will make it nicer to only have asingle `WasiView` trait and additionally make it easier tosimultaneously implement all of WASIp{1,2,3}.* Fix build of C API* Fix build of `wasmtime serve` List of files: /wasmtime-44.0.1/crates/wasi/src/cli/stdout.rs Fri, 01 Aug 2025 23:40:08 +0000 Alex Crichton <alex@alexcrichton.com>