Xiangpeng Hao

I'm also thinking about this: ```rust #[cxx::bridge] mod ffi { struct A { a: f32, } extern "Rust" { #[struct = "A"] fn foo() -> A; #[struct = "A"] fn...

Hi sorry for the late reply, I added a docker file to the repo, can you try that and see if you can reproduce the results?

I'm not familiar with Windows or macOS; contributions are welcomed!

I checked out the latest code, but unfortunately it doesn't seem to fix the problem... This can be reproduced by running the `test_process` test case ```bash env RUSTFLAGS="-Z sanitizer=memory" cargo...

A possible workaround is to do `MaybeUninit::::zeroed()` instead of `uninit()` The root cause might be that the `libc` is not properly instrumented (not [compiled with](https://doc.rust-lang.org/beta/unstable-book/compiler-flags/sanitizer.html#build-scripts-and-procedural-macros) `-fsanitize=memory`, and I don't know...

I only got doc tests failed after switching to `zeroed()`. The errors are likely not related to this change, it's just that the lib tests get the chance to run...

Setting OMP_NESTED globally can be dangerous though, as some data structures may use OMP and they might have their control

I'm happy to add c interfaces and look forward to seeing the pull request.

The Congee projects starts with 8 fix-sized byte keys. In the future we might elevate this restriction.

Congee should be linearizable. We need some tools to check linearizbility: https://arxiv.org/pdf/1504.00204.pdf and https://github.com/anishathalye/porcupine