You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bridge: implement JSExport, Objective-C blocks, and interop completion evidence #160
Parent: #138
Depends on: Objective-C inventory, core behavior, and managed lifetime children
Complete callable/exported Objective-C interop and the final bridge evidence matrix.
Acceptance:
Implement Objective-C block to JavaScript callable conversion and JavaScript function to block/callable invocation with argument/return conversion and exception propagation.
Interop implementation and evidence are complete through 7b37b20: 108/108 declarations, 17-row system-JSC parity (189ef5b0eefd1054), same-VM cross-context exported receiver/constructor/prototype coverage, typed Objective-C blocks, JavaScript JSValue callable invocation, 200-cycle autorelease teardown, ASan+UBSan, and 0-byte Apple leak output. WebKit itself rejects block-typed JSExport arguments because Objective-C exposes only the opaque @? encoding; zig-js likewise avoids inventing an unsafe callable ABI. This issue remains open only to close parent #138 after #159 finishes conditional collection and fault-injection work.
Activity
feat(objc): bridge typed Objective-C blocks (#160)
test(objc): diff typed blocks with JSC (#160)
feat(objc): export protocol methods and properties (#160)
test(objc): diff JSExport instances with JSC (#160)
feat(objc): export classes and renamed selectors (#160)
test(objc): diff JSExport classes with JSC (#160)
fix(objc): preserve cross-context value identity (#160)
docs(objc): publish cross-context parity evidence (#160)
test(objc): diff cross-context exports with JSC (#160)
docs(objc): publish cross-context export evidence (#160)
test(objc): add sanitized lifetime evidence (#160)
docs(objc): publish lifetime evidence matrix (#160)
chrisbbreuer commentedon Jul 17, 2026
Interop implementation and evidence are complete through 7b37b20: 108/108 declarations, 17-row system-JSC parity (
189ef5b0eefd1054), same-VM cross-context exported receiver/constructor/prototype coverage, typed Objective-C blocks, JavaScriptJSValuecallable invocation, 200-cycle autorelease teardown, ASan+UBSan, and 0-byte Apple leak output. WebKit itself rejects block-typed JSExport arguments because Objective-C exposes only the opaque@?encoding; zig-js likewise avoids inventing an unsafe callable ABI. This issue remains open only to close parent #138 after #159 finishes conditional collection and fault-injection work.chrisbbreuer commentedon Jul 17, 2026
Completed through f29ca38. The bridge covers typed Objective-C blocks, JavaScript callable JSValue invocation, JSExport protocols/classes/properties/constructors/renames, all inventoried conversions, same-VM cross-context identity and receiver semantics, cross-VM rejection, 108/108 inventory, 18-row system-JSC parity (
360c1ad3ccf51d6b), 200-cycle lifetime stress, ASan+UBSan, deterministic faults, 0-byte leaks, and published README/API reproduction.