opaque-pointer-rs

Generic functions to work with opaque pointers when use FFI to expose Rust structs

Basic usage

With this crate you can manage raw pointers easily to expose structs that will be use as opaque pointers from C or C++ calling to Rust functions to use it. This can be used with cbindgen crate with option parse.parse_deps = true for it will generate opaque C/C++ structs to use pointers in the arguments.

You can find more information about using Rust from other languages in The Rust FFI Omnibus objects section of Jake Goulding.

Examples

Creating FFIs to use a Rust's struct methods from C or C++:

```rust struct TestIt { value: u8 }

impl TestIt { pub fn add(&mut self, value: u8) { self.value += value } pub fn get(&self) -> u8 { self.value } }

/// Ownership will NOT control the heap-allocated memory until own it back.

[no_mangle]

pub extern fn testitnew(value: u8) -> *mut TestIt { return opaque_pointer::raw(TestIt { value }); }

/// Drop (free memory of) Rust's TestIt object as usually.

[no_mangle]

pub extern fn testitfree(testit: *mut TestIt) { let testit = unsafe { opaquepointer::free(testit) }; }

[no_mangle]

pub extern fn testitadd(testit: *mut TestIt, value: u8) -> Result<(), opaquepointer::error::PointerError> { let testit = unsafe { opaquepointer::mutobject(testit)? }; test_it.add(value); // Here will NOT be dropped, the pointer continues been valid. return Ok(()); }

[no_mangle]

pub extern fn testitget(testit: *const TestIt) -> Result { let testit = unsafe { opaquepointer::object(testit)? }; return Ok(test_it.get()); // Here will NOT be dropped, the pointer continues been valid. } ```

The previous example is compiled when tests are run. If you have an error with that code, please, open a issue.

Features

• std: activated by default, it is required for c-types FFI.
• alloc: required if compile without std.
• c-types: FFI for C types, requires std feature.
• panic-if-null: it will check if a pointer is null to panic before to use it.

Panic & unwind in FFI functions

As a good resume see comment in gtk-rs issue #78:

Currently any unwinding across extern "C" functions is UB, even if all those functions happens to be implemented in Rust. That's part of what that WG is working on solving. For example this adds support for an extern "C-unwind" ABI that explicitly allows unwinding (and AFAIU causes unwinding through extern "C" to abort as it should).

And the mentioned pull request #76570 of Rust.

Also see comment in Rust issue #58794 and Rust issue #58760:

The default was changed to abort-by-default in extern functions in this PR. This is tracking the stabilization of the #[unwind(allowed)] (and #[unwind(abort)]) attributes.

Also Rust pull request #55982:

This PR changes the behavior of generated code to be sound-by-default. If an extern fn is unwound (panicked through) then it immediately aborts the program. Put another way, no extern fn can unwind.

And Rust issue #52652:

This UB is not mentioned in any later release notes.