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
The idea: A lot of the ergonomics of the framework would be easier if we had instances of zaplib instead of relying on imports.
You don’t have to worry about calling initialize/initializeWorker twice, because initializing gives you the object to call callRust on and not at the top level
you can move some of the awkward let variables at the global scope in the module into easy to read instance vars. less global vars in general.
much easier to find in your codebase where zaplib first gets used
you’ll need this anyways if you want multiple wasm binaries
a bit easier to unify the api between worker and main thread (for example initializePort would be on the module not on the instance)
The text was updated successfully, but these errors were encountered:
The idea: A lot of the ergonomics of the framework would be easier if we had instances of zaplib instead of relying on imports.
The text was updated successfully, but these errors were encountered: