Worth keeping android/interoperability/cpp.html and chromium/interoperability-with-cpp.html in sync? · google/comprehensive-rust#1523

(5 comments) (0 reactions) (0 assignees)Rust (32,954 stars) (2,009 forks)batch import

enhancementgood first issue

Description

Android-specific and Chromium-specific parts of the course both talk about using https://cxx.rs for C++/Rust interop. Is it worth it to somehow unify some of the content?

In particular, both introductory slides (at android/interoperability/cpp.html and chromium/interoperability-with-cpp.html) have a diagram of how cxx works, but Chromium also has additional speaker notes where it lists some benefits (over manually authoring the bindings).

PS. Some of the content will need to remain Android-specific and/or Chromium-specific:

Error handling (Chromium disables C++ exceptions, so Android slides don't apply)
Integration with Chromium's gn templates vs genrules on Android side

/cc @adetaylor

Contributor guide

Tech stack: rustcpp
Domain: documentation
Issue type: documentation
Difficulty: 2
Estimated time: half day
Activity status: stale
Clarity: clear
Prerequisites: Familiarity with Rust course structureBasic understanding of CXX interop
Newbie friendliness: 80
Research direction: Start by examining the two files: android/interoperability/cpp.html and chromium/interoperability with cpp.html. Compare the introductory slides and speaker notes, especially the diagram and benefits of cxx. Determine if common content can be extracted into a shared file, while keeping Android specific and Chromium specific parts separate. Check existing comments for maintainer insights, particularly from @adetaylor. Then propose a plan for unification with minimal duplication.