Changes in func.h

c09aa380 - deprecate `[Typed]Func::post_return[_async]` and make them no-ops (#12498)

Tue, 03 Feb 2026 19:13:45 +0000

deprecate `[Typed]Func::post_return[_async]` and make them no-ops (#12498)* deprecate `[Typed]Func::post_return[_async]` and make them no-opsWith the advent of the Component Model concurrency ABI and it's `task.return`intrinsic, post-return functions have been informally deprecated and areexpected to be removed for WASI 1.0 and the corresponding stable edition of theComponent Model. Consequently, it does not make sense anymore to requireembedders to explicitly call the post-return function after using`[Typed]Func::call[_async]`.As of this commit, `[Typed]Func::post_return[_async]` are no-ops. Instead, thepost-return function is called automatically as part of`[Typed]Func::call[_async]` if present, which is how`[Typed]Func::call_concurrent` has worked all along. In addition, this commitfixes and tests a couple of cases where the task and/or thread was beingdisposed of before the post-return function was called.* address review feedback* test post-return function in more scenariosSpecifically, I've split the `invoke_post_return` test into multiple tests:- using `TypedFunc::call`- using `TypedFunc::call_async` with concurrency support enabled- using `TypedFunc::call_async` with concurrency support disabled- using `Func::call_async` with concurrency support disabled- using `TypedFunc::call_concurrent`* remove GCC/clang-specific deprecation attributeThis broke the MSVC build.* bless bindgen output* remove obsolete post-return functions and fieldsNow that post-return calls are handled internally without requiring explicitaction by the embedder, we can avoid unnecessary bookkeeping. List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/component/func.h

39ec36ca - Fill out type information for components in C API (#11937)

Wed, 05 Nov 2025 18:56:02 +0000

Fill out type information for components in C API (#11937)* Fill out type information for components in C APII've concluded that I'll want this for wasmtime-py so this fills outtype reflection for various items in the C API. This then additionallyextends the C++ API as well.prtest:full* Update crates/c-api/include/wasmtime/component/types/func.hCo-authored-by: Joel Dice ---------Co-authored-by: Joel Dice List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/component/func.h

e33836c0 - Refactor the representation of component::Func (#10914)

Tue, 03 Jun 2025 21:23:21 +0000

Refactor the representation of component::Func (#10914)* Expand on FIXME commentsIn case it takes awhile to get to them...* Remove `FuncData::types`This can always be inferred from the instance itself.* Add an `ExportIndex` to `FuncData`This will soon be used to remove most other fields, but for now justhave it hanging out there.* Remove `FuncData::component_instance` field* Remove `FuncData::post_return`* Remove `FuncData::ty`* Remove `FuncData::export`* Remove `FuncData::options`* Remove `FuncData::post_return_arg`This field was moved to `ComponentInstance` as the stateful storage ofthe last function return value.* Refactor the representation of `component::Func`This commit updates the implementation of `component::Func` to beindex-based like all other exported items are now in Wasmtime. Thisnecessitated a new `StoreComponentInstanceId` abstraction similar to`StoreInstanceId`. Additionally the `component_instance_replace`function was entirely removed as it's no longer necessary. List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/component/func.h

53701b21 - c-api: component-model: Function post return, more values (#10841)

Tue, 27 May 2025 21:16:06 +0000

c-api: component-model: Function post return, more values (#10841)* c-api: component-model: `wasmtime_component_post_return()`* c-api: component-model: Tuple values* c-api: component-model: Variant valuesThis required `wasmtime_component_val_new()` List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/component/func.h

b2c64de1 - c-api: component-model: Values and function calling (#10697)

Fri, 23 May 2025 14:05:50 +0000

c-api: component-model: Values and function calling (#10697)* c-api: component-model: Primitive values* c-api: component-model: Function calling* A test* Take args as mut to avoid copying* String and char* Rethink value ownership semantics, add list values* Record values* Make take Rust values as refs in `::from()` functionsLater we can provide implementations that take it as a value to avoidcopying* Define host functions* `wasmtime_component_valrecord_new()`* Use `u32` instead of `char` as its not ffi safe* Test records and strings in c-api -> vm -> host func -> vm -> c-api* `wasmtime_component_vallist_new()`* Test lists* Fix formatting* Use existing `declare_vecs` construct* Add rest of helper functions* Add documentation* Fix multiline comments* Third time's the charm* Fourth time's the charm prtest:full* Doxygen file headers* Fix other missing documentation* Small fix to docs List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/component/func.h

ce3c1a72 - c-api: component-model: Lookup function from an instance (#10675)

Mon, 28 Apr 2025 19:23:36 +0000

c-api: component-model: Lookup function from an instance (#10675)* c-api: component-model: Lookup function from an instance* c-api: component-model: Take strings as `wasm_name_t`* Use export indices* Shared `CHECK_ERR` macro* Pass names as a pointer and a size, return nullable pointers* Use `std::str::from_utf8()` instead of `str::from_utf8()`* Remove doc link? List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/component/func.h