@JSclassTextProcessor{@JSinit(transform:@escaping(String)->String)@JSfunc processWithPerson(_ person:Person, formatter:(Person)->String)-> String@JS func makePersonCreator(defaultName:String)->(String)->Person}

constprocessor=newexports.TextProcessor((text)=>text.toUpperCase());constperson=newexports.Person("Alice");constresult=processor.processWithPerson(person,(p)=>`${p.name}:${p.greet()}`);constcreator=processor.makePersonCreator("Default");constp1=creator("Bob");

TypeScript:

exportinterfaceTextProcessorextendsSwiftHeapObject{processWithPerson(person:Person,formatter:(arg0:Person)=>string):string;makePersonCreator(defaultName:string):(arg0:string)=>Person;}

Technical Changes

• Extended type system to supportBridgeType.closure(ClosureSignature)
• Updated Swift parser to detect closure parameters in function declarations
• Generate Swift helper enums (_BJS_Closure_*) for each unique closure signature
• Generate JavaScript callback registry and invoke functions, needed to expose_exports and_bjs to support that
• Map closure signatures to TypeScript function types
• Automatic memory management in both directions, needed to addbridgeJSLowerParameterWithRetain to support optionalSwiftHeapObject

Supported Features

• ✅ Closure parameters with any supported type
• ✅ Closure return values
• ✅@escaping closures
• ✅ Optional closures and optional parameters/returns
• ✅ All existing BridgeJS types (primitives, String, enums, Swift classes)
• ❌ Closure-typed properties (parameters/returns only)
• ❌ Async/throwing closures

Testing

Added comprehensive snapshot and runtime tests for closure parameters, returns, optionals, and Swift heap objects in closures.

Documentation

Extended current documentation with newExporting-Swift-Closure.md