en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh#311d023a Simplify C++ binding definitions (#11936)This commit adds a shared macro to simplify ownership management in theC++ API and to additionally have a uniform API across types. This isinspired by the component model work where I felt like I wascopy/pasting quite a lot and wanted to cut down on that. List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh Tue, 04 Nov 2025 23:51:20 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh#adff9d9d Fix externref/anyref ownership in C/C++ API (#11799)* Fix externref/anyref ownership in C/C++ APIThis commit is a follow-up to #11514 which was discovered throughfailing tests in the wasmtime-py repository when updating to Wasmtime37.0.0. Effectively a combination of bugs in the Rust API meant that itwasn't possible to use `externref` or `anyref` bindings correctly. TheRust changes in this commit are:* `wasmtime_val_unroot` correctly drops the value now as opposed to effectively being a noop from before (typo of using `as_externref` vs `from_externref`).* `wasmtime_{anyref,externref,val}_t` now have a `Drop` implementation in Rust to correctly drop them if a value in Rust is dropped. This is required to correctly manage memory in the `wasmtime_func_{call,new}` implementations, for example.* `wasmtime_{anyref,externref,val}_clone` no longer have an unnecessary context parameter.* `wasmtime_{anyref,externref,val}_unroot` no longer have an unnecessary context parameter.Changes in the C/C++ APIs are:* `Result::{ok,err}_ref` APIs were added in addition to the preexisting rvalue accessors.* Loading/storing typed arguments now has an overload for `const T&` and `T&&` which behaves differently. Notably transferring ownership for `T&&` and not for `const T&`. This means that passing parameters when calling a wasm function uses `const T&`, but passing results from a host import uses `T&&`.* `TypedFunc::call` now uses `const Params&` instead of `Params` to explicitly specify it doesn't modify the parameters and forces using the `const T&` store method.* `Store::gc` is now a convenience method for `store.context().gc()`* `ExternRef`, `AnyRef`, and `Val` now have ownership semantics and destructors. This matches the spirit of #11514 for Rust but models it in C++ as well. This required filling out move/copy constructors/assignments.* The explicit `ExternRef` now takes `std::any` instead of `T`.* Minor issues related to ownership are fixed in `Val` bindings.Valgrind was used to ensure that there were no leaks for the test suitewhich additionally resulted in a number of `*_delete` calls being addedto tests using the C API (accidental omissions).The original goal of this change was to be a patch release for 37.0.1 toenable updating wasmtime-py to the 37.0.x releases of Wasmtime. In theend though the changes here were broad enough that I no longer feel thatthis is a good idea, so wasmtime-py will be skipping the 37 version ofWasmtime.* Run `clang-format`prtest:full List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh Tue, 07 Oct 2025 16:36:13 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh#313f23d8 Test C/C++ headers can be included in isolation (#10694)* Test C/C++ headers can be included in isolationI frequently make mistakes about this, so I figure it's good to at leasttry to test this. It's not possible to fully test AFAIK but this ishopefully at least something.* Fix header discovery location* Don't test `conf.h.in`* Try to fix windows CI List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh Tue, 29 Apr 2025 16:25:31 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh#a045eaa9 Run `clang-format` over more files (#10689)We were already running it over most `*.c` files and other ones butforgot the `*.hh` and `*.cc` extensions which are being used for C++bindings, so add those in and then run the formatter. List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh Mon, 28 Apr 2025 20:38:14 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh#453bb9a4 Split C++ Func/Table/Memory/Global to their own headers (#10688)I did my best to separate out headers but I don't understand enough C++to fully sever `val.hh` and `func.hh` so they sort of circularlyreference each other now. List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh Mon, 28 Apr 2025 19:41:13 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh#d460709e Move C++ `Config` to its own header (#10634)Also bind APIs which were added since this was created. Also copy oversome `#define` guards for the C methods into the C++ header as well. Andfinally update tests for what's added. List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh Tue, 22 Apr 2025 16:23:01 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh#0467d6f9 Sketch out merging the C/C++ APIs (#10600)* Sketch out merging the C/C++ APIsWith the merging of the C++ API into this repository in #10582 it opensup some interesting questions about how to organize the C++ API.Externally it was all entirely a single file, but naturally this isn'tgreat for evolution as it's just one giant tangled header. Instead thiscommit sketches out a possible different path forward which is toprovide the C++ API as a sibling to the C API in preexisting headerfiles. For example this moves the `Error` class to the `error.h` headerfile as an example.My rough hope would be that in the long-term we could deprecate/removethe `wasmtime.hh` header file and instead "just" have all the C++ APIsin the normal header files (e.g. `wasmtime.h`). Additionally the splitof the C API in separate header files would be amenable to a similarsplit of the C++ API too where the API you see is basically conditionalon the language mode of whatever's including the headers.I'll note though I've not seen prior art in doing this. I'm not aware ofany other project which exports both a C and C++ API in its headerfiles. That being said I'm not sure how many other projects would fallin such a bucket.* Split out `error.hh` to its own file List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/error.hh Mon, 21 Apr 2025 20:47:20 +0000 Alex Crichton <alex@alexcrichton.com>