Lines Matching refs:unsafe

55 and need to leverage that fact from Rust, you must provide your own unsafe
69 unsafe impl Send for ffi::MyType {}
70 unsafe impl Sync for ffi::MyType {}
92 the C++ function is safe or unsafe to be called from Rust.
95 each signature inside as safe-to-call or unsafe-to-call. If an extern block
96 contains at least one safe-to-call signature, it must be written as an `unsafe
97 extern` block, which serves as an item level unsafe block to indicate that an
103     unsafe extern "C++" {
110         unsafe fn g();  // unsafe to call
139     unsafe extern "C++" {
203     unsafe extern "C++" {
215     unsafe extern "C++" {
223 #### Integrating with bindgen-generated or handwritten unsafe bindings
228 By writing the unsafe `ExternType` impl, the programmer asserts that the C++
237 unsafe impl ExternType for folly_sys::StringPiece {
244     unsafe extern "C++" {
278 # unsafe impl cxx::ExternType for TypeName {