Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update seamless-rust-cpp.md #195

Merged
merged 1 commit into from
Dec 18, 2024
Merged

Update seamless-rust-cpp.md #195

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 20 additions & 13 deletions src/2025h1/seamless-rust-cpp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
# Evaluate approaches for seamless use of C++ APIs from Rust
# Evaluate approaches for seamless interop between C++ and Rust

| Metadata | |
|----------|-----------------------|
| Owner(s) | @baumanj and @tmandry |
| Teams | [lang] [compiler] |
| Status | Proposed |
| Metadata | |
| -------- | ---------------------------- |
| Owner(s) | @baumanj and @tmandry |
| Teams | [lang] [compiler] [libs-api] |
| Status | Proposed |

## Summary

Expand Down Expand Up @@ -78,7 +78,13 @@ These mismatches point to the limitations of such approaches. If we attempt to s

### The next 6 months

We do not propose any specific deliverables over the next six months. We only propose a discussion with the language and compiler teams that takes a serious look at the problem space and what it would take to solve it. This discussion should incorporate lessons from existing projects and lay the foundation for future explorations and engagements.
We do not propose any specific deliverables over the next six months. We only propose a discussion with the Language, Compiler, and Libs-API teams that takes a serious look at the problem space and what it would take to solve it. This discussion should incorporate lessons from existing projects and lay the foundation for future explorations and engagements.

Possible discussion topics include:

* Coverage of rich C++ APIs, including those that make use of language features like templates, (partial) specialization, and argument-dependent lookup. (Lang + Compiler)
* Seamless use of "vocabulary types" like strings, vectors, and hashmaps, including the various kinds of conversions in source and at the ABI level. (Lang + Libs-API)
* A standard IDL for describing a Rust API/ABI that can be produced by the Rust compiler. (Lang + Compiler)

### The "shiny future" we are working towards

Expand Down Expand Up @@ -110,12 +116,13 @@ In addition, it proposes the following axioms:

**Owner:** @baumanj and @tmandry

| Task | Owner(s) or team(s) | Notes |
| ---------------------------- | --------------------------- | ------------------------------------------------------------------------ |
| Discussion and moral support | ![Team][] [lang] [compiler] | |
| Design meeting | ![Team][] [lang] [compiler] | 2 meetings expected; ideal audience is lang team with compiler team reps |
| Author design doc | @tmandry can drive | |
| Author design doc | ![Help wanted][] | |
| Task | Owner(s) or team(s) | Notes |
| ---------------------------- | -------------------------------------- | --------------------------------------- |
| Discussion and moral support | ![Team][] [lang] [compiler] [libs-api] | |
| Design meeting | ![Team][] [lang] [compiler] [libs-api] | 2-3 meetings expected; all involve lang |
| Author design doc | @tmandry can drive | |
| Author design doc | ![Help wanted][] | |
| Author design doc | ![Help wanted][] | |

## Frequently asked questions

Expand Down
Loading