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.