Allow either order of `derive(CtorFrom_Default)` / `#[recursively_pinned]`. Primary error: the layout of `CtorInitializedFields` is ignored, I can just clear the attrs! Oopsie woopsie. However, even if we do that, there's other problems that make these macros compose very poorly in the original order. Apparently, ideally, either order should work, but this is definitely messy to support. Another solution would be to detect if they're misordered and swap the order in the macro. I think this is worth deferring to some later time to do "properly" -- this only matters during the process of porting a C++ class to Rust, and that's somewhat of a theoretical concern given the current state of interop. PiperOrigin-RevId: 463065300
Extremely experimental interop tooling for C++ and Rust.
Please don‘t use, this is an experiment and we don’t yet know where will it take us. There will be breaking changes without warning. Unfortunately, we can't take contributions at this point.
$ apt install clang lld bazel $ git clone git@github.com:google/crubit.git $ cd crubit $ bazel build --linkopt=-fuse-ld=/usr/bin/ld.lld //rs_bindings_from_cc:rs_bindings_from_cc_impl
$ git clone https://github.com/llvm/llvm-project $ cd llvm-project $ CC=clang CXX=clang++ cmake -S llvm -B build -DLLVM_ENABLE_PROJECTS='clang' -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=install $ cmake --build build -j $ # wait... $ cmake --install build $ cd ../crubit $ LLVM_INSTALL_PATH=../llvm-project/install bazel build //rs_bindings_from_cc:rs_bindings_from_cc_impl