Move C API into separate crate? about blazesym

[anakryiko]

Makes sense, assuming it's easy to keep them in sync and prevent accidental blazesym-c breakage?

[danielocfb]

Makes sense, assuming it's easy to keep them in sync and prevent accidental blazesym-c breakage?

I think so; they would be in the same repository and workspace and so once you change one the other would see changes.

[danielocfb]

There seems to be precedent for such a split:
https://github.com/rust-lang/rustc-demangle#usage-from-non-rust-languages
https://github.com/rust-lang/rustc-demangle/tree/main/crates/capi

[danielocfb]

I started prototyping this proposal but it turns out the issue is that because our Rust API declares a bunch of types as non-exhaustive, once we cross crate boundaries we are running into issues constructing the corresponding objects. We could probably work around that somehow with special cases and whatnot, but at least at this point it's unlikely to be worth the trouble.

I'll keep the code around, should I come up with a good solution, but we can probably declare this proposal as failed-at-prototype-stage.

[d-e-s-o]

Reopening this as I keep coming back to wanting the separation.