this post was submitted on 09 Mar 2024
48 points (100.0% liked)

Rust

6005 readers
5 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
EdTheLegendary@programming.dev
kahnclusions@programming.dev
torcherist@programming.dev
48
Secure by Design: Google’s Perspective on Memory Safety (security.googleblog.com)
submitted 8 months ago by Timely_Jellyfish_2077@programming.dev to c/rust@programming.dev
16 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] sugar_in_your_tea@sh.itjust.works 2 points 8 months ago

FFI is just calling Rust directly from something else (or vice versa), and has pretty much no performance compromises. The main downside is potential safety implications at the FFI boundary (i.e. need to guarantee Rust doesn't release C++ memory or vice versa), but if you're already fine with gRPC performance penalties, you can just copy everything at the boundary and not worry about it.

It's basically the way Python native modules work, and can be used between any C-compatible languages.