Luca Barbato

@nirbheek do you have a test suite we can share?

thank you a lot :)

I'm conflicted about this PR, it would be better if this kind of logic is part of cargo itself and possibly not rely on pkg-config being stable on dealing with...

Isn't this a problem you have with cargo as well? Please try this and report back, but I'm afraid it should be addressed at cargo level instead. ```toml [package.metadata.capi.library] rustflags...

It is a cargo issue, I thought you had problems with building something using cargo-c, today had been quite Monday. You can see if building `cargo` with `cargo` shows the...

Yes, it touches what is inside the variants, the variants themselves remain untouched see [here](https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=393946cace5788a9441229ed1ef61827) ```rust use serde::{Serialize, Deserialize}; use serde_json; // 1.0.140 #[derive(Serialize, Deserialize)] #[serde(rename_all_fields = "UPPERCASE")] enum E...

The `cargo ctest` tries to build the target with specific rustflags that the tests shouldn't use so the current solution is a bit hacky. If you want to delve in...

I never had the chance to look into it and how it could be integrated, ctest is useful mainly if you want to test your C API using the rust...

[serde_norway](https://crates.io/crates/serde_norway/reverse_dependencies) seems also an option.

The upcoming rayon solves its problems neatly:  And we have `compute_block_importances` and `compute_lookahead_data` that could happily live in a separate thread and not stall the rest of the encoding.