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
If the workers were merged, then it would make sense merge all of the Native/JS/Wasm generation into a single worker and task. They don't differ significantly: Native uses KlibResolver.Native and JS/Wasm uses KlibResolver.JS, and this can be controlled with a Platform input property.
It's a bit delicate to do such refactoring at the moment because the Native worker is in the public API, but will be easier once the visibility of workers is limited #211.
The text was updated successfully, but these errors were encountered:
Source code generation is very similar for Native, JS, and Wasm platforms.
This could most likely be simplified.
If the workers were merged, then it would make sense merge all of the Native/JS/Wasm generation into a single worker and task. They don't differ significantly: Native uses
KlibResolver.Native
and JS/Wasm usesKlibResolver.JS
, and this can be controlled with aPlatform
input property.It's a bit delicate to do such refactoring at the moment because the Native worker is in the public API, but will be easier once the visibility of workers is limited #211.
The text was updated successfully, but these errors were encountered: