Provide Rust only interface #46
Description
Having the C FFI interface exported via no_mangle functions when brotli is used as an rlib dependency causes issues when linking into a project that also depends on the C brotli library (see Nullus157/async-compression#83).
I'm not sure what the best approach for this would be; as someone that has not worked on a library exposing a C ABI, it seems to me that this would work better as a separate crate simply wrapping a Rustic implementation, instead of being combined into a single crate. Another idea I had was putting the ffi module behind a cargo feature. But neither of these feel like the perfect solution to me.