Julien Cretin

> * once one has a shared object .so with the main functionality (which we should be able to generate from the rust codebase, right @ia0?) For Rust in general...

[Here](https://github.com/google/magika/compare/main...ia0:magika:cdylib)'s an example on how to build a dynamic library in Rust and use it from C. Ultimately we'll build such a `magika-api` crate and provide a `.h` and `.so`...

> Hello, ia0. > I have successfully compiled magika into a.so file according to the steps you provided. However, during the process of using the C API, I encountered the...

It looks to me like a problem with your platform. Maybe it's too old or it's missing some library. If you can't resolve it on your own, your best bet...

> The std currently assumes that they _are_ promised to have the same layout (https://doc.rust-lang.org/src/core/str/converts.rs.html#172) The layout for transmute doesn't matter. I guess the safety comment was about `str` and...

> What would you suggest for how the documented guarantees should be strengthened to match what the PR author obviously wants? I'm going to assume "what the PR author obviously...

> your point is really to make a more rigorous definition of "layout" That would be an editorial question. I'm not saying that. I'm saying a new concept of "representation...

> When I say "layout" (and I suspect when the std says the same), I am including field offsets in that Yes, layout is "size + align + field offset...

> It seems to be an obviously preexisting problem. Please open a PR against the reference to address the concerns you have. The PR already exists, it's https://github.com/rust-lang/reference/pull/1664. Not sure...

What is the status of this feature? Is it only available in the CLI with the `--show-annotations` flag? Is it planned to also be supported in the GitHub Action and...