For 2.0 we want to add a native Rust API, but we still plan to support users using a C API.
The C API will have breaking changes too - we want to namely don't having any implicit devices and providing more clear errors.
We don't want 2 entry points for every call in libkrun - C API should be a layer built on top of Rust API. The new C API and Rust API should be reasonably similar which is why I think we need to think about this together.
For 2.0 we want to add a native Rust API, but we still plan to support users using a C API.
The C API will have breaking changes too - we want to namely don't having any implicit devices and providing more clear errors.
We don't want 2 entry points for every call in libkrun - C API should be a layer built on top of Rust API. The new C API and Rust API should be reasonably similar which is why I think we need to think about this together.