Changes in rust.rs

1b59b579 - Add support for map type (#12216)

Mon, 09 Mar 2026 23:34:21 +0000

Add support for map type (#12216)* Add support for map typeSigned-off-by: Yordis Prieto * Add Map and MapEntry classes to support key/value pairs in component modelThis commit introduces the Map and MapEntry classes, enabling the representation of map values in the component model. The Map class allows for the creation and iteration of key/value pairs, enhancing the functionality of the wasmtime component API. Additionally, the .gitignore file is updated to exclude build artifacts from the crates/c-api directory.* Add wasm_component_model_map configuration support* Format code* Format C code* Enhance component model to support HashMap typeThis commit introduces support for HashMap in the component model, allowing maps to be represented as list> in the canonical ABI. It includes implementations for the ComponentType, Lower, and Lift traits for HashMap, enabling type checking, lowering to flat representations, and lifting from memory. Additionally, the maximum depth for type generation in the fuzzing utility is updated to accommodate the new map type.* Refactor component configuration to introduce map supportThis commit removes the previous wasm features configuration and adds new functions for creating a map-configured engine. The `map_config` and `map_engine` functions are introduced to facilitate the use of the component model with maps in tests, ensuring that the engine is properly configured for map types in the component model.* Add new WAST test for map types and remove map type definitions from existing testsThis commit introduces a new WAST test file specifically for testing various map types in the component model. Additionally, it removes the redundant map type definitions from the existing types.wast file to streamline the test suite.* Update component fuzzing and dynamic tests to replace call_and_post_return with call* Format code* Refactor HashMap usage in typed.rs to use wasmtime_environ collections* Fix HashMap initialization and insertion to handle potential errors in typed.rs* Refactor HashMap handling in typed.rs to use lower_map_iter for improved iteration and memory management. Introduce new implementations for ComponentType, Lower, and Lift traits for std::collections::HashMap, enhancing support for map types in the component model.* Fix map adapter trampoline compilation and alignment bugsThe translate_map function had two categories of bugs preventing mapadapter trampolines from working:1. Wasm stack discipline: local_set_new_tmp emits LocalSet which pops from the stack, but was called when the stack was empty (to "pre-allocate" locals). Fixed by computing values first, then calling local_set_new_tmp to consume them—matching translate_list's pattern. Also removed an erroneous LocalTee that left an orphan value on the stack. Affected: src_byte_len, dst_byte_len, cur_src_ptr, cur_dst_ptr.2. Pointer advancement: after value translation, the pointer still points at the value start. The code only advanced by trailing padding instead of value_size + trailing_padding, causing every loop iteration to re-read the same memory.Also fixes entry layout to use proper record alignment rules (entryalign = max(key_align, value_align), value at aligned offset).* Refactor map entry layout calculations to use canonical ABI* Remove unnecessary clone of map pairs during loweringVal::Map already holds Vec<(Val, Val)> which derefs to &[(Val, Val)],matching lower_map's signature directly. The intermediate Vec allocationand deep clone of every key/value pair was redundant.* Deduplicate map lift logic between HashMap implementations* Deduplicate list and map sequence translation scaffolding* Fix cargo fmt formatting issues* Deduplicate map typecheck logic* Deduplicate map lowering with linear_lower_map_to_flat and linear_lower_map_to_memory helpers* Clean up lift_try_map: use drop, move TryHashMap import to module scope* Fix CI: arbtest overflow and no-std HashMap lift_map- component_fuzz: use saturating_sub in generate_hashable_key to prevent underflow when fuel is 0 and Enum variant is chosen- typed: remove incorrect ? operators in lift_map for hashbrown::HashMap (with_capacity and insert don't return Result)* Store map tuple layout in TypeMapCompute map entry ABI and value offsets once during type building, and reuse that metadata in runtime map lift/lower paths instead of recalculating tuple layout at each call site.* Refactor map ABI argument passingBundle map lift/lower layout and type metadata into a small MapAbi32 helper so map helper calls stay concise without changing behavior.* Fix CI: enable component_model_map in fuzzing and handle map in arbitrary_valThe fuzzer's component_api oracle was generating map types but the enginedidn't have the map feature enabled, and arbitrary_val had no arm forType::Map. Enable component_model_map in the store helper (matching howcomponent_model_async is forced on) and implement arbitrary value generationfor map types.---------Signed-off-by: Yordis Prieto List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

d2fbd2de - Update to wasm-tools 245 (#12571)

Thu, 12 Feb 2026 15:38:22 +0000

Update to wasm-tools 245 (#12571)* Intrinsics updates* Remove ds_store* Update to wasm-tools 245* Add vets* Fixup tests* Add missing feature for `indexmap`---------Co-authored-by: Sy Brand List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

e63dd69f - Update wasm-tools dependencies (#12254)

Wed, 07 Jan 2026 18:44:38 +0000

Update wasm-tools dependencies (#12254)* Update wasm-tools dependenciesBrings in binary-parsing support for the WIT `map` type as well as thewasm compact-imports proposal. Neither of these are enabled by defaultand will continue to be rejected, but it'll now be possible to supportthem without needing to update dependencies.* Add vets* Update test expectations, add testsCloses #12166 List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

b4475438 - refactor `{Stream,Future}|{Reader,Writer}` APIs and internals (#11325)

Wed, 30 Jul 2025 16:40:41 +0000

refactor `{Stream,Future}|{Reader,Writer}` APIs and internals (#11325)* refactor `{Stream,Future}|{Reader,Writer}` APIs and internalsThis makes a several changes to how `{Stream,Future}|{Reader,Writer}` work tomake them more efficient and, in some ways, more ergonomic:- The background tasks have been removed, allowing reads and writes to complete without task context switching. We now only allocate and use oneshot channels lazily when the other end is not yet ready; this improves real world performance benchmarks (e.g. wasi-http request handling) considerably.- Instances of `{Stream,Future}Reader` can now be lifted and lowered directly; no need for `Host{Stream,Future}` anymore.- The type parameter for `Stream{Reader,Writer}` no longer refers to the buffer type -- just the payload type (i.e. `StreamReader` instead of `StreamReader>`), meaning any buffer type may be used for a given read or write operation. This also means the compiler needs help with type inference less often when calling `Instance::stream`.- Instances of `{Stream,Future}|{Reader,Writer}` now require access to the store in order to be disposed of properly. I've added RAII wrapper structs (`WithAccessor[AndValue]`) to help with this, and also updated `Store::drop` and `Instance::run_concurrent` to ensure the store thread-local is set when dropping futures closing over `&Accessor`s.- In order to ensure that resources containing `{Stream,Future}|{Reader,Writer}` instances are disposed of properly, I've added `LinkerInstance::resource_concurrent` and have updated `wasmtime-wit-bindgen` to use it. This gives resource drop functions access to a `StoreContextMut` via an `Accessor`, allowing the stream and future handles to be disposed of. - In order to make this work, I had to change `Accessor::instance` from a `Instance` to an `Option`, which is awkward but temporary since we're planning to remove `Accessor::instance` entirely once we've moved concurrent state from `ComponentInstance` to `Store`.That problem of disposal is definitely the most awkward part of all this. Insimple cases, it's easy enough to ensure that read and write handles aredisposed of properly, but both `wasmtime-wasi` and `wasmtime-wasi-http` havesome pretty complicated functions where handles are passed between tasks and/orstored inside resources, so it can be tricky to ensure proper disposal on allcode paths. I'm open to ideas for improving this, but I suspect we'll need newRust language features (e.g. linear types) to make it truly ergonomic, robust,and efficient.While testing the above, I discovered an issue with `Instance::poll_until` suchthat it would prematurely give up and return a "deadlock" trap error, believingthat there was no further work to do, even though the future passed to it wasready to resolve the next time it was polled. I've fixed this by polling it onelast time and only trapping if it returns pending.Note that I've moved a few associated functions from `ConcurrentState` to`Instance` (e.g. `guest_drop_writable` and others) since they now need access tothe store; they're unchanged otherwise. Apologies for the diff noise.Finally, I've tweaked how `wasmtime serve` to poll the guest for content beforehanding the response to Hyper, which helps performance by ensuring the firstcontent chunk can be sent with the same TCP packet as the beginning of theresponse.Signed-off-by: Joel Dice fix wasi p3 build and test failuresSigned-off-by: Joel Dice use `ManuallyDrop` instead of `Option` in `Dropper`This allows us to drop its `value` field in-place, i.e. without moving it,thereby upholding the `Pin` guarantee.Signed-off-by: Joel Dice address review comments- Remove `DropWithStoreAndValue` and friends; go back to taking a `fn() -> T` parameter in `Instance::future` instead- Make `DropWithStore::drop[_with]` take `&mut self` instead of `self`- Make `WithAccessor` and `DropWithStore` private - Instead, I've added public `Guarded{Stream,Future}{Reader,Writer}` types for RAII - and also `{Stream,Future}{Reader,Writer}::close[_with]` methods- Use RAII in `FutureReader::read` and `FutureWriter::write` to ensure handles are dropped if the `Future` is droppedSigned-off-by: Joel Dice * lower host stream/future writes in background taskThis avoids unsoundness due to guest realloc calls while there are host embedderframes on the stack.Signed-off-by: Joel Dice * fix `tcp.rs` regressionsSigned-off-by: Joel Dice ---------Signed-off-by: Joel Dice List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

beca86b0 - Re-enable concurrent bindings generation tests (#10972)

Mon, 09 Jun 2025 14:15:18 +0000

Re-enable concurrent bindings generation tests (#10972)* Re-enable concurrent bindings generation testsThis commit re-enables tests for bindings generation for concurrentcalls in the main repo after all syncs have now finished with wasip3.This additionally adds some skeleton APIs that the bindings generatoruses which are necessary to get tests passing.* Update test expectations List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

90ac295e - Update Wasmtime to the 2024 Rust Edition (#10806)

Mon, 19 May 2025 16:40:55 +0000

Update Wasmtime to the 2024 Rust Edition (#10806)* Update Wasmtime to the 2024 Rust EditionNow that our MSRV supports the 2024 edition it's possible to make thisswitch. This commit moves Wasmtime to the 2024 Edition to keepup-to-date with Rust idioms and access many of the edition featuresexclusive to the 2024 edition.prtest:full* Reformat with the 2024 edition List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

e682be4e - Update wasm-tools crates (#10731)

Mon, 05 May 2025 20:47:11 +0000

Update wasm-tools crates (#10731)* Update wasm-tools cratesMinor API changes, mostly just stubbing out support forfixed-size-lists.* Update vets* Update some test expectations List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

4d0a43fd - wasmtime-wit-bindgen: nonfunctional changes to internals (#10578)

Mon, 14 Apr 2025 23:49:43 +0000

wasmtime-wit-bindgen: nonfunctional changes to internals (#10578)* wasmtime-wit-bindgen: transform type printing to return stringskeep all used print_ functions, but otherwise NFC refactor to returnString instead of push strs to the output.* reusable typedfunc signatureprtest:full* clippy List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

b8e3fbe9 - Update wasm-tools to the latest revision (#10314)

Wed, 05 Mar 2025 22:32:54 +0000

Update wasm-tools to the latest revision (#10314)* Update wasm-tools to the latest revision* Update component async bits for new intrinsics* Ignore options for now* I truly, and fundamentally, do not understand `cargo vet`* Fix a test List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

af31e80d - wasmtime-wit-bindgen: emit a definition for all types in a wit interface (#10311)

Fri, 28 Feb 2025 19:06:58 +0000

wasmtime-wit-bindgen: emit a definition for all types in a wit interface (#10311)* wasmtime-wit-bindgen: emit a definition for all types in a witThe calculation of TypeInfo only reaches types which are passed to orfrom a function. For types which are not reachable, default to thedefining them according to the ownership setting given to bindgen.I have my doubts that `with`-reuse of bindgen types actually worksproperly when bindgen is set to Ownership::Borrowing but thats outof scope for this PR, which is to fix #10090* component-macro: bless bindgen test output List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

6e221e7a - wasmtime-wit-bindgen: gen is a reserved keyword in the lexer starting in 2024 edition (#10308)

Fri, 28 Feb 2025 15:53:00 +0000

wasmtime-wit-bindgen: gen is a reserved keyword in the lexer starting in 2024 edition (#10308) List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

636435f1 - async/stream/future support for wasmtime-wit-bindgen (#10044)

Wed, 22 Jan 2025 17:19:46 +0000

async/stream/future support for wasmtime-wit-bindgen (#10044)* async/stream/future support for wasmtime-wit-bindgenI've split this out of #9582 to make review easier.This patch adds async/stream/future/error-context support to the host bindinggenerator, along with placeholder type and function definitions in the`wasmtime` crate which the generated bindings can refer to. Seehttps://github.com/dicej/rfcs/blob/component-async/accepted/component-model-async.md#componentbindgen-updatesfor the design and rationale.Note that I've added temporary `[patch.crates-io]` overrides in Cargo.toml untilhttps://github.com/bytecodealliance/wit-bindgen/pull/1130 andhttps://github.com/bytecodealliance/wasm-tools/pull/1978 have been released.Also note that we emit a `T: 'static` bound for `AsContextMut` whengenerating bindings with `concurrent_imports: true`. This is only because`rustc` insists that the closure we're passing to`LinkerInstance::func_wrap_concurrent` captures the lifetime of `T` despite mybest efforts to convince it otherwise. Alex and I suspect this is a limitationin the compiler, and I asked about it on the rust-lang Zulip, but we haven'tbeen able to determine a workaround so far.Signed-off-by: Joel Dice remove obsolete TODO commentSigned-off-by: Joel Dice make `futures` dep optionalSigned-off-by: Joel Dice update `wasm-tools` and `wit-bindgen`Signed-off-by: Joel Dice * run cargo vetSigned-off-by: Joel Dice ---------Signed-off-by: Joel Dice List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

4c5f250f - Update wasm-tools crates (#9952)

Wed, 08 Jan 2025 22:16:39 +0000

Update wasm-tools crates (#9952)* Update wasm-tools cratesPull in recent updates and denying memory64 support in components duringvalidation.* Fix renamings in wave* Fix some bindgen tests List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

a0442ea0 - Enforce `uninlined_format_args` for the workspace (#9065)

Mon, 05 Aug 2024 09:59:59 +0000

Enforce `uninlined_format_args` for the workspace (#9065)* Enforce `uninlined_format_args` for the workspace* fix: failing `Monolith Checks` job* fix: formatting List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

44220746 - Overhaul and improve documentation of `bindgen!` (#8727)

Mon, 03 Jun 2024 13:50:05 +0000

Overhaul and improve documentation of `bindgen!` (#8727)This is another take at improving the documentation for `bindgen!` inWasmtime. This commit takes a leaf out of the book ofbytecodealliance/wit-bindgen#871 to organize the documentation of themacro a bit more rather than having one giant doc block that can bedifficult to explore. The macro's documentation itself is now mostly areference of all the options that can be specified. There is now a newdocumentation-only module which serves a few purposes:* Individual examples are organized per-submodule to be a bit more digestable.* Each example has an example of the generated code in addition to the source code used for each example.* All examples are tested on CI to compile (none are run).My hope is that this makes it easier to expand the docs here furtherover time with niche features as they arise or with various options thatthe macro has. This is one of the lynchpins of Wasmtime's support forthe component model so it seems pretty important to have a goodonboarding experience here.Along the way I've implemented a few more niche options for the`bindgen!` macro that I found necessary, such as configuring the`wasmtime` crate and where it's located. List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

81a89169 - Add support for `#![no_std]` to the `wasmtime` crate (#8533)

Sat, 04 May 2024 22:02:26 +0000

Add support for `#![no_std]` to the `wasmtime` crate (#8533)* Always fall back to custom platform for WasmtimeThis commit updates Wasmtime's platform support to no longer require anopt-in `RUSTFLAGS` `--cfg` flag to be specified. With `no_std` becomingofficially supported this should provide a better onboarding experiencewhere the fallback custom platform is used. This will cause linkererrors if the symbols aren't implemented and searching/googling shouldlead back to our docs/repo (eventually, hopefully).* Change Wasmtime's TLS state to a single pointerThis commit updates the management of TLS to rely on just a singlepointer rather than a pair of a pointer and a `bool`. Additionallymanagement of the TLS state is pushed into platform-specific modules toenable different means of managing it, namely the "custom" platform nowhas a C function required to implement TLS state for Wasmtime.* Delay conversion to `Instant` in atomic intrinsicsThe `Duration` type is available in `no_std` but the `Instant` type isnot. The intention is to only support the `threads` proposal if `std` isactive but to assist with this split push the `Duration` further intoWasmtime to avoid using a type that can't be mentioned in `no_std`.* Gate more parts of Wasmtime on the `profiling` featureMove `serde_json` to an optional dependency and gate the guest profilerentirely on the `profiling` feature.* Refactor conversion to `anyhow::Error` in `wasmtime-environ`Have a dedicated trait for consuming `self` in addition to a`Result`-friendly trait.* Gate `gimli` in Wasmtime on `addr2line`Cut down the dependency list if `addr2line` isn't enabled since thenthe dependency is not used. While here additionally lift the versionrequirement for `addr2line` up to the workspace level.* Update `bindgen!` to have `no_std`-compatible outputPull most types from Wasmtime's `__internal` module as the source oftruth.* Use an `Option` for `gc_store` instead of `OnceCell`No need for synchronization here when mutability is already available inthe necessary contexts.* Enable embedder-defined host feature detection* Add `#![no_std]` support to the `wasmtime` crateThis commit enables compiling the `runtime`, `gc`, and `component-model`features of the `wasmtime` crate on targets that do not have `std`. Thistags the crate as `#![no_std]` and then updates everything internally toimport from `core` or `alloc` and adapt for the various idioms. Thisended up requiring some relatively extensive changes, but nothing tootoo bad in the grand scheme of things.* Require `std` for the perfmap profiling agentprtest:full* Fix build on wasm* Fix windows build* Remove unused import* Fix Windows/Unix build without `std` feature* Fix some doc links* Remove unused import* Fix build of wasi-common in isolation* Fix no_std build on macos* Re-fix build* Fix standalone build of wasmtime-cli-flags* Resolve a merge conflict* Review comments* Remove unused import List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

e78605e8 - Update wasm-tools family of crates (#8242)

Tue, 26 Mar 2024 17:10:53 +0000

Update wasm-tools family of crates (#8242)Closes #8241 List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

a8209097 - Fix more nightly warnings (#7907)

Fri, 09 Feb 2024 22:36:00 +0000

Fix more nightly warnings (#7907)Additionally give `-Zcheck-cfg` a spin with Cargo and fix some mistakeswith our `--cfg` and `#[cfg]` directives. List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

878a243a - Host resources wit-bindgen code generation (#6886)

Wed, 30 Aug 2023 03:14:02 +0000

Host resources wit-bindgen code generation (#6886)* added trap to resource dtor* basic resources* fixed signature and trait bounds* fixed static function* fixed trait signature* basic resources* added result to resource drop* reverted formatting* added doc comment to resource `dtor`* fixed merge issue* fixed another merge issue* added resource import codegen test* Revert changes to `Cargo.lock`* Update `Cargo.lock` with the wit-bindgen update* Add `cargo vet` entries for new crates* Restore old-style of printing types in bindgenAvoid collecting resources-as-we-go in favor of doing that moredeclaratively elsewhere. Additionally handle imported-vs-exportedresource via the order that interfaces are visited.* Update the shape of resource traits:* Use `&mut self` instead of `StoreContextMut`* Make resource traits as supertraits of the `Host` trait generated for each resource.* More uniformly handle types/returns with resource methods.* Fix derivations of `Clone` and `Copy` for where handles are contained.* Fix generation of handle typedefs* Support resources-in-worlds* Remove now-duplicate functionThis is now the same as the preexisting `generate_function_trait_sig`* Fix classifying handles as imported or exportedThis determination happens by looking up the origin definition of aresource, not the leaf possibly-aliased type.* Fix chains-of-use of resourcesResources don't have their representation asserted since the bare typeitself doesn't implement `ComponentType`, but otherwise generate typealiases the same way as other type aliases.* Revert `Cargo.lock` changesNo need to update `wit-bindgen` to 0.10.0 just yet, that'll happen in afuture update if necessary.* Add basic runtime tests for resources* fixed merge issue---------Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs

35902366 - Remove component union types (#6913)

Sat, 26 Aug 2023 19:51:23 +0000

Remove component union types (#6913)- Bump wasm-tools deps- Use new TypeSectionReader::into_iter_err_on_gc_types method List of files: /wasmtime-44.0.1/crates/wit-bindgen/src/rust.rs