libaegis

> The main advantage is that cross-compilation to many targets is supported out of the box For the readers who aren't familiar: The code for running test and then cross-compiling (on one machine and OS) for different target platforms is: https://github.com/jedisct1/libaegis/blob/main/.github/workf... and the only zig file in the repo which drives the build process is: https://github.com/jedisct1/libaegis/blob/main/build.zig

I also now always use Zig to write tests and benchmarks for C code. This is for example the case in libaegis: https://github.com/jedisct1/libaegis Calling C functions from Zig is easy (C headers can be imported directly) and doesn't have any overhead. So I can take advantage of the convenience of Zig, even if the tested code only requires a C compiler. I also now always add Zig build files as an alternative to make/libtool/automake/cmake/meson/etc. The main advantage is that cross-compilation to many targets is supported out of the box, including to WebAssembly. So I can quickly test if the C code compiles fine before actually trying to run it on an emulator.

Libsodium has been around for a while, so probably the reason it was posted is that version 1.0.19 was just released: https://github.com/jedisct1/libsodium/releases/tag/1.0.19-RE... Updated NuGet and Swift packages are going to be uploaded soon. AEGIS-128X and 256X are not there yet, but if you need them, they are available in libaegis: https://github.com/jedisct1/libaegis All the code from libaegis will eventually be merged into libsodium, including the incremental update API which is especially useful for TLS.