|
Revision tags: dev, v36.0.9, v44.0.1, v43.0.2, v36.0.8, v24.0.8, v44.0.0, v43.0.1, v42.0.2, v36.0.7, v24.0.7, v43.0.0, v42.0.1, v41.0.4, v42.0.0, v40.0.4, v36.0.6, v24.0.6, v41.0.3, v41.0.2, v41.0.1, v36.0.5, v40.0.3, v41.0.0, v36.0.4, v39.0.2, v40.0.2, v40.0.1, v40.0.0, v39.0.1, v39.0.0, v38.0.4, v37.0.3, v36.0.3, v24.0.5, v38.0.3, v38.0.2, v38.0.1, v37.0.2, v37.0.1, v37.0.0, v36.0.2, v36.0.1, v36.0.0, v35.0.0, v24.0.4, v33.0.2, v34.0.2, v34.0.1, v33.0.1, v24.0.3, v32.0.1, v34.0.0, v33.0.0 |
|
| #
a045eaa9 |
| 28-Apr-2025 |
Alex Crichton <[email protected]> |
Run `clang-format` over more files (#10689)
We were already running it over most `*.c` files and other ones but
forgot the `*.hh` and `*.cc` extensions which are being used for C++
bindings, so add
Run `clang-format` over more files (#10689)
We were already running it over most `*.c` files and other ones but
forgot the `*.hh` and `*.cc` extensions which are being used for C++
bindings, so add those in and then run the formatter.
show more ...
|
| #
0467d6f9 |
| 21-Apr-2025 |
Alex Crichton <[email protected]> |
Sketch out merging the C/C++ APIs (#10600)
* Sketch out merging the C/C++ APIs
With the merging of the C++ API into this repository in #10582 it opens
up some interesting questions about how to org
Sketch out merging the C/C++ APIs (#10600)
* Sketch out merging the C/C++ APIs
With the merging of the C++ API into this repository in #10582 it opens
up some interesting questions about how to organize the C++ API.
Externally it was all entirely a single file, but naturally this isn't
great for evolution as it's just one giant tangled header. Instead this
commit sketches out a possible different path forward which is to
provide the C++ API as a sibling to the C API in preexisting header
files. For example this moves the `Error` class to the `error.h` header
file as an example.
My rough hope would be that in the long-term we could deprecate/remove
the `wasmtime.hh` header file and instead "just" have all the C++ APIs
in the normal header files (e.g. `wasmtime.h`). Additionally the split
of the C API in separate header files would be amenable to a similar
split of the C++ API too where the API you see is basically conditional
on 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 of
any other project which exports both a C and C++ API in its header
files. That being said I'm not sure how many other projects would fall
in such a bucket.
* Split out `error.hh` to its own file
show more ...
|