en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/tests/error.cc#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/tests/error.cc 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/tests/error.cc#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/tests/error.cc Mon, 21 Apr 2025 20:47:20 +0000 Alex Crichton <alex@alexcrichton.com>