Managing Memory Interoperability: Pointers and Values in Carbon
Learn how Carbon manages memory interoperability with C++ using value and pointer semantics to achieve zero-overhead performance without sacrificing safety.
Loading…
ReadMeFeed / Community knowledge
#cpp-interop
Real questions. Useful conversations. Find the people who know your stack.
Calling C++ from Carbon: Packages, Extern Blocks, and Common Pitfalls
Learn how to call existing C++ functions from Carbon by declaring a package, using an extern "C++" block, and following best practices to avoid common pitfalls. The guide includes a step‑by‑step example and a practical checklist.
Carbon's Pointer and Reference Model: An Architecture Note on C++ Interoperability Boundaries
Carbon's experimental pointer and reference model aims to make C++ interoperability memory-safe without wrapper overhead. This architecture note examines the trust boundary, operational checks, and failure modes.
Managing the C++ Migration: Carbon's Bidirectional Interop Strategy
Carbon aims to solve the 'rewrite' problem by providing bidirectional interoperability with C++, allowing for incremental migration without the overhead of traditional glue code.
Calling C++ Functions from Carbon Using the Bridge Mechanism
Learn how to call C++ functions directly from Carbon using its built‑in bridge, with a concrete example, build steps, and a list of current limitations.
Using Checked Pointers in Carbon for Safer C++ Interop
Explains how Carbon’s checked pointers add runtime bounds and null safety to raw pointers from C++, with a worked example, trade‑offs, and steps to try the feature.
Jule's C++ Compilation Strategy: A Practical Engineering Decision
Jule compiles to C++ instead of machine code, trading custom backend maintenance for instant platform support and seamless C++ interop. Learn how this affects memory safety, debugging, and the build pipeline.
juleCarbon's C++ Interoperability: An Architecture Note on Incremental Migration
Carbon's bidirectional C++ interoperability via extern "C++" linkage enables incremental migration without wrappers. This architecture note covers the minimal design, trust boundaries, CI verification steps, failure modes, and conditions that would force a redesign.
Calling a C++ Function from Carbon and Exposing Carbon Types to C++
Guide to calling a C++ function from Carbon and exposing Carbon types to C++ using the Carbon toolchain and Bazel.
bazel