Avoid dangling item ids for skipped template specializations.

Before this CL, `class_template_instantiations_for_current_target_` was
populated before checking `import_status`.  This could lead to dangling
`top_level_item_ids`.  This CL fixes this problem and adds a handful of
`.with_context(...)` calls that helped investigate where the dangling
item ids were present.

Before this CL `rs_bindings_from_cc/test/consume_absl:main` test would
trigger a crash/error/panic in `rs_bindings_from_cc`.  After this CL,
the test merely hits some `redefinition of '__rust_thunk...'` errors in
the generated `absl/numeric/int128_rust_api_impl.cc`.

PiperOrigin-RevId: 471302280
5 files changed
tree: ebde837f4a5f284b5792a8c8d57b0c3e0883cf69
  1. .bazelci/
  2. bazel/
  3. cc_template/
  4. common/
  5. docs/
  6. lifetime_analysis/
  7. lifetime_annotations/
  8. migrator/
  9. nullability_verification/
  10. rs_bindings_from_cc/
  11. .bazelrc
  12. .gitignore
  13. BUILD
  14. Cargo.Bazel.lock
  15. CODE_OF_CONDUCT
  16. CONTRIBUTING
  17. LICENSE
  18. README.md
  19. WORKSPACE
README.md

Crubit: C++/Rust Bidirectional Interop Tool

Build status

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.

Building Crubit

$ 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

Using a prebuilt LLVM tree

$ 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