arraybridge

ArrayBridge owns explicit array-framework conversion, memory-type declarations, stack utilities, dtype policy, GPU stream/OOM helpers, and cleanup for scientific applications.

• Installation
  • Optional frameworks
  • Development and documentation
• Quick start
  • Detection and conversion
  • Callable declarations
  • Stacks
• User guide
  • Framework names
• Conversion system
  • Device semantics
  • Failures
• Memory declaration decorators
  • Direct-call behavior
  • Dtype policy
• Stack utilities
• GPU lifecycle
• Advanced extension topics
• API reference
  • Public imports
  • Documented public surface
• Examples
  • Basic conversion
  • Decorator declarations
  • Multi-framework boundary
  • Example Categories
• Contributing
  • Framework extensions
• Continuous integration

Boundary rule

Conversion is explicit. convert_memory moves values between frameworks. Decorators declare callable input/output memory types and runtime policies; they do not perform cross-framework conversion on direct calls.

ArrayBridge does not own a host application’s compiler, function catalog, or resource scheduler. Hosts consume the declarations and plan conversions/devices at their own boundary.