moonbit-c-binding

To bind a C library to MoonBit, you write `extern "c"` declarations for C functions and create C stub files using `moonbit.h`. You then configure `native-stub` and `link.native` in your `moon.pkg` to link the native build.

Memory management across the FFI boundary uses `#borrow` and `#owned` ownership annotations. You wrap C pointers with external objects and finalizers to ensure safe memory handling and prevent leaks.

You handle string conversion by managing encoding differences between MoonBit's UTF-16 strings and C's UTF-8 strings. The binding process requires explicit conversion logic to safely pass strings across the FFI boundary.

Yes, you can use AddressSanitizer to validate MoonBit C bindings. It enables robust memory bug detection during native integration, ensuring your external object finalizers and pointer management work correctly.

You implement C callbacks in MoonBit using callback trampolines. These trampolines bridge C function calls back into MoonBit code safely while maintaining proper context and memory ownership.

You need to configure `native-stub` and `link.native` settings in your `moon.pkg` or `moon.pkg.json` file. This configuration directs the MoonBit build system to compile and link your C stubs correctly.