...like the past few decades of Python/Ruby/Node/etc wrapping C-ABI libraries from any language?<p><a href="https://docs.python.org/3/extending/extending.html" rel="nofollow">https://docs.python.org/3/extending/extending.html</a><p><a href="https://nodejs.org/dist/latest-v20.x/docs/api/n-api.html#node-api" rel="nofollow">https://nodejs.org/dist/latest-v20.x/docs/api/n-api.html#nod...</a><p><a href="https://docs.python.org/3/library/ctypes.html" rel="nofollow">https://docs.python.org/3/library/ctypes.html</a><p><a href="https://swig.org" rel="nofollow">https://swig.org</a><p>When using Zig functions and structs on the low side there are some nice opportunities for making the low/high interface more automatic at comptime, especially when you're jointly compiling (your Zig code + a Zig-based Python interpreter + your Python code) together into one WASM blob.<p><i>Disclaimer/public-commitment-to-getting-it-released: I've written most of a Python interpreter in Zig as part of another project. (just the basics — won't be big and professional like CPython.) I'll reply here eventually when it's done, available as FLOSS, and ready to say "high-low".</i>