Safe and efficient C++ interoperability via non-escapable types and lifetimes.
Introduction Safely interacting with unsafe code is challenging. The C++ interoperability layer has limited safeguards in place to mitigate some sources of unsafety including hiding some APIs (like methods returning iterators) and exposing them with an “Unsafe” suffix. Unfortunately, these are based on simple syntactic heuristics that are incomplete (like identifying methods that return pointer like objects) and therefore do not provide sufficient safety guarantees and do not provide a way to sa…
Read in full here:
This thread was posted by one of our members via one of our news source trackers.