Lena Code Interop

Topaz is one of the languages supported in Lena Code's conversion workflows. It is not Lena Code's core surface or intermediate language; this page focuses on practical interop paths, where Topaz code can be translated into other ecosystems and external code can be lifted back into Topaz without rewriting by hand.

Before/After Snapshots

Rust → TypeScript

pub fn greet(name: &str) -> String {
    format!("Hello, {}!", name)
}

export function greet(name: string): string {
  return `Hello, ${name}!`;
}

Rust → Topaz

pub fn add(a: i32, b: i32) -> i32 {
    a + b
}

function add(a: int, b: int) -> int {
    a + b
}

These examples illustrate the shape-preserving goal of Lena Code: types, control flow, and naming survive the conversion so teams can continue working in their preferred language.

Getting Access

• Visit lenacode.com to review supported languages and usage guidance.
• Automated flows, including bidirectional bulk conversions, can be configured to match your team's operating model. Use support channels if you need onboarding.

Notes & Constraints

• The scenarios above show representative conversion patterns; output format can be adjusted by project settings.
• Conversions run directly in the Lena Code workspace and can be operated to fit your workflow.
• Keep Result-first and pattern-matching idioms in mind when moving into Topaz—the translator preserves them when they exist in the source.