Gleam Erlang Interop

Call Erlang code from Gleam by declaring external functions with typed signatures using Gleam's external function syntax, then invoke them as normal Gleam functions. The Skill provides typed interfaces that maintain type safety across the language boundary while accessing Erlang modules and OTP behaviors.

Yes. Gleam-Erlang interop enables integration with NIFs (native implemented functions) and ports for low-level BEAM ecosystem access. Declare external functions that wrap NIF calls or port communication, maintaining type safety at the Gleam boundary.

Handle Erlang data types safely by mapping them to typed Gleam aliases at the interop boundary. This approach ensures type correctness when exchanging data between Gleam and Erlang code, preventing runtime errors from type mismatches.

Maintain type safety by declaring external functions with explicit typed signatures for Erlang library calls. The Skill enforces boundary correctness through Gleam's type system, ensuring Erlang function inputs and outputs conform to declared types.

Gleam supports BEAM ecosystem integrations including OTP behaviors, Erlang modules, NIFs, and ports. Declare external functions to access these components while keeping Gleam's type guarantees intact across the interop boundary.