There is a world in the C and C++ commercial ecosystems that will never adopt tooling that doesn't support shipping some form of binary libraries.
I remember reading somewhere that there was no plan for binary packages in Zig, given its FOSS point of view.
That's the only way to expose a C++ library to other languages though, or even make a DLL written for one C++ compiler consumable by a program written with another C++ compiler.
It's a limitation for sure, but definitely not a show stopper.
e.g. https://pkg.odin-lang.org/vendor/directx/d3d12/#ICommandQueu...
* command_queue^.id3d12commandqueue_vtable^.BeginEvent(command_queue, MetaData, pData, Size)
* command_queue.id3d12commandqueue_vtable.BeginEvent(command_queue, MetaData, pData, Size) // no need for the explicit dereferencing with ^
* command_queue.BeginEvent(command_queue, MetaData, pData, Size) // the vtable has `using` on it
* command_queue->BeginEvent(MetaData, pData, Size) // the -> operator will pass the value into the first argument
The `->` operator was added specifically for COM API stuff, and has been useful for the Objective-C stuff too.
https://github.com/andrewrk/ffmpeg
Why not use a system package? Well, because the user's system might not have such a package. They might be on Windows, for example. Or their package might be out of date. [Or the system might have chosen sides in a nasty fork war](http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html).
So, while system packages are nice for end users, they might not always satisfy the needs of upstream application developers.