This web content discusses the limitations of C++’s Safety Profiles in detecting memory safety defects in existing C++ code. It examines the inability of the profiles to recover crucial information from function declarations, such as aliasing, lifetimes, and safeness requirements, leading to false positives and negatives in safety analysis. The need for explicit annotations in function types, akin to Rust’s borrow type, is highlighted as essential for achieving memory safety. The content emphasizes the importance of separating safe and unsafe functions, with the use of safe-specifiers, to ensure soundness preconditions are met and to prevent undefined behavior. The paper reveals the challenges in enforcing memory safety without proper annotations and transitive properties in function declarations.
https://www.circle-lang.org/draft-profiles.html