<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in values.cc</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>39ec36ca - Fill out type information for components in C API  (#11937)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/component/values.cc#39ec36ca</link>
        <description>Fill out type information for components in C API  (#11937)* Fill out type information for components in C APII&apos;ve concluded that I&apos;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 &lt;joel.dice@fermyon.com&gt;---------Co-authored-by: Joel Dice &lt;joel.dice@fermyon.com&gt;

            List of files:
            /wasmtime-44.0.1/crates/c-api/tests/component/values.cc</description>
        <pubDate>Wed, 05 Nov 2025 18:56:02 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>dbc21cde - Support resources in the C API of Wasmtime (#11920)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/component/values.cc#dbc21cde</link>
        <description>Support resources in the C API of Wasmtime (#11920)This commit builds on #11885 to build out support for resources incomponents in the C API of Wasmtime. Support is effectively the same asin Rust except more things are behind pointers and `ResourceDynamic` isused under the hood instead of `Resource&lt;T&gt;` due to the lack ofmonomorphization. Tests have been updated to go through some varioussituations of ensuring that guest and host resources are representableand can be manipulated.

            List of files:
            /wasmtime-44.0.1/crates/c-api/tests/component/values.cc</description>
        <pubDate>Wed, 22 Oct 2025 23:40:44 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>cde2e04f - Fill out more of the C++ API for components (#11889)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/component/values.cc#cde2e04f</link>
        <description>Fill out more of the C++ API for components (#11889)* capi: Add a C++ API for `component::Linker`Just a bare-bones API for now with functionality that&apos;s possible to fillout. Notably instantiation and defining functions is not yet possible inC++. Some more feature-parity is also added with the core linkers aswell.* capi: Add bindings for component instances* capi: Delete wasip2.h header fileUpon reflection I realize that this is not actually necessary and isotherwise a duplicate of the functionality in `wasi.h`. All of thefunctionality in `wasi.h` is already supported to power WASIp2-definedAPIs in a linker, which is enabled by the `WasiView` trait redirectingto the `WasiView for WasiP1Ctx` implementation. This is similar to howthe `wasmtime` CLI works where a P1 context is always created and thenit&apos;s conditionally used for either core wasm or components.Effectively this is a deletion of duplicate functionality in the C APIbut no underlying functionality is lost. Translating information topreexisting WASI calls will work the same as using the wasip2 APIs before.* capi: Start bindings for component functions* capi: Bind component values in the C++ API* capi: Finish bindings for component functions/linkersAll the pieces are now in place to use the C++ API in testing.* Fix compilation of CLI* Fix compile on MSVC* Try again to fix msvc compat* Fix `get_f32` and `get_f64` return values* Fix signed return values* Remove no-longer-needed `capi_transfer` function* Try to fix msvc again* Remove std::optional constructor of `Val`* Fix another namespace clash on msvc* One day I surely may understand a fraction of either C++ or MSVC, buttoday is not that day.* Document internal macro* Add other internal docs

            List of files:
            /wasmtime-44.0.1/crates/c-api/tests/component/values.cc</description>
        <pubDate>Tue, 21 Oct 2025 19:27:10 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>579ec46b - capi: Start filling out C++ API for components (#11880)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/component/values.cc#579ec46b</link>
        <description>capi: Start filling out C++ API for components (#11880)* capi: Start filling out C++ API for componentsI&apos;d like to write some fancier tests soon for this, but I&apos;m not a fan ofwriting C, so this commit starts to fill out the C++ API for componentsby adding a few wrapper classes. Like the rest of the C++ API this isall built as a wrapper around the C API.This commit introduces a `Component` type and an `ExportIndex` type togo along with it. This binds the `component.h` header file in C++. Thisalso starts a convention of `capi` methods to access the underlyingpointer/value as a conventional way to mix the C/C++ APIs which willallow gradually migrating tests to C++.* Fix clippy lint

            List of files:
            /wasmtime-44.0.1/crates/c-api/tests/component/values.cc</description>
        <pubDate>Mon, 20 Oct 2025 16:47:31 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>9a26c101 - c-api: component-model: Flags type (#10873)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/component/values.cc#9a26c101</link>
        <description>c-api: component-model: Flags type (#10873)* c-api: component-model: Flags type* Hand make `wasm_name_t::default()` implementation

            List of files:
            /wasmtime-44.0.1/crates/c-api/tests/component/values.cc</description>
        <pubDate>Fri, 30 May 2025 21:34:36 +0000</pubDate>
        <dc:creator>MangoPeachGrape &lt;191630121+MangoPeachGrape@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>90a2351b - c-api: component-model: Result types (#10864)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/component/values.cc#90a2351b</link>
        <description>c-api: component-model: Result types (#10864)

            List of files:
            /wasmtime-44.0.1/crates/c-api/tests/component/values.cc</description>
        <pubDate>Fri, 30 May 2025 04:51:13 +0000</pubDate>
        <dc:creator>MangoPeachGrape &lt;191630121+MangoPeachGrape@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>fa89f323 - c-api: component-model: Enum and option values (#10858)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/component/values.cc#fa89f323</link>
        <description>c-api: component-model: Enum and option values (#10858)* c-api: component-model: Enum values* c-api: component-model: Option values

            List of files:
            /wasmtime-44.0.1/crates/c-api/tests/component/values.cc</description>
        <pubDate>Thu, 29 May 2025 15:29:10 +0000</pubDate>
        <dc:creator>MangoPeachGrape &lt;191630121+MangoPeachGrape@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>53701b21 - c-api: component-model: Function post return, more values (#10841)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/component/values.cc#53701b21</link>
        <description>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/tests/component/values.cc</description>
        <pubDate>Tue, 27 May 2025 21:16:06 +0000</pubDate>
        <dc:creator>MangoPeachGrape &lt;191630121+MangoPeachGrape@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>b2c64de1 - c-api: component-model: Values and function calling (#10697)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/component/values.cc#b2c64de1</link>
        <description>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 -&gt; vm -&gt; host func -&gt; vm -&gt; 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&apos;s the charm* Fourth time&apos;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/tests/component/values.cc</description>
        <pubDate>Fri, 23 May 2025 14:05:50 +0000</pubDate>
        <dc:creator>MangoPeachGrape &lt;191630121+MangoPeachGrape@users.noreply.github.com&gt;</dc:creator>
    </item>
</channel>
</rss>
