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
Zipline is currently built on Kotlin/JS, which creates some complexity and limitations:
Lots of things are built on JS runtime APIs, including setTimeout, console, and JSON
Intermediate .js source files going from Kotlin source to QuickJS bytecode
Zipline needs QuickJS bytecode parsing to inject .kt line numbers
No debugger
It’d be nicer to use WASM instead of QuickJS bytecode as Zipline’s standard instruction format. We can’t do this yet as Kotlin’s WASM support is still extremely experimental. But if/when that matures we should support it and create a gentle upgrade path from QuickJS to WASM.
The text was updated successfully, but these errors were encountered:
Zipline is currently built on Kotlin/JS, which creates some complexity and limitations:
setTimeout
,console
, andJSON
.js
source files going from Kotlin source to QuickJS bytecode.kt
line numbersIt’d be nicer to use WASM instead of QuickJS bytecode as Zipline’s standard instruction format. We can’t do this yet as Kotlin’s WASM support is still extremely experimental. But if/when that matures we should support it and create a gentle upgrade path from QuickJS to WASM.
The text was updated successfully, but these errors were encountered: