google/comprehensive-rust

Worth keeping android/interoperability/cpp.html and chromium/interoperability-with-cpp.html in sync?

Open

#1,523 建立於 2023年11月29日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)Rust (32,954 star) (2,009 fork)batch import
enhancementgood first issue

描述

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:

/cc @adetaylor

貢獻者指南

技術棧
rustcpp
領域
documentation
議題類型
documentation
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Familiarity with Rust course structureBasic understanding of CXX interop
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
80
研究方向
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.