Ffi Design

Usage Guidelines

1. Safety: Design safe wrappers around unsafe FFI calls
2. Marshaling: Document type marshaling rules explicitly
3. Ownership: Make memory ownership clear at FFI boundaries
4. Callbacks: Handle callback lifetimes carefully
5. Strings: Handle string encoding conversions correctly (UTF-8, UTF-16)

Output Schema

{
  "type": "object",
  "properties": {
    "callingConventions": {
      "type": "array",
      "items": { "type": "string" }
    },
    "marshalingRules": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "sourceType": { "type": "string" },
          "targetType": { "type": "string" }
        }
      }
    },
    "callbackSupport": { "type": "boolean" },
    "generatedFiles": {
      "type": "array",
      "items": { "type": "string" }
    }
  }
}