Native C++ FFI in the same manner as D
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Friday Apr 12, 2013 at 14:04 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/5853
This issue was labelled with: A-an-interesting-project, A-ffi, E-hard, I-wishlist, P-low in the Rust repository
@sanxiyn and @jdm have expressed interest in doing this, possibly in the 0.8 cycle.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the earlier discussion in rust-lang/rust#5853 and the linked Reddit C FFI discussion. Clarify the intended scope for native C++ FFI and compare it with the referenced D approach; done means the project has an agreed design and implementation path for that interoperability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100