Export a C API

[bilelmoussaoui]

To fully replace libsecret. I wouldn't try to make it glib-y as that would be painful, depends on whoever does the work.

[A6GibKm]

I kinda want to leave glib out of the equation, but it could buy so much for us: Language bindings.

[bilelmoussaoui]

I kinda want to leave glib out of the equation, but it could buy so much for us: Language bindings.

I don't care about other languages. They can create bindings from the exported C API if they want to

[sophie-h]

I don't think it's a good idea to try to replace a glib API by not providing a glib API

[ueno]

I would suggest starting with the simple API, which should be sufficient for most applications and independent of glib, though supporting async operations might be tricky.

[bilelmoussaoui]

I don't think it's a good idea to try to replace a glib API by not providing a glib API

The problem is converting a Rust future to a gio::Task and then wrapping it in a C API would be just painful to maintain and very error-prone. But I leave that to whoever want to implement it to see what is easier to achieve