Carbon pointer safety rules when passing objects across the C++ interop boundary
Context I am evaluating Carbon (the experimental C++ successor language) for a gradual migration of an existing C++ codebase. The design goal under review is how Carbon's memory-safety model interacts with its bidirectional C++ interoperability, specifically when ownership of an object crosses the language boundary. Uncertainty Carbon aims to reduce classic