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
Because Sourceror is not part of js-slang, the pre-processing step which handles imports & exports does not work with Sourceror. This means that the WebAssembly variants of Source do not support multi-file programs currently. Instead, only the entrypoint file is passed to Sourceror currently:
"Source WebAssembly" has always been a kind of "proof of concept". There will be various efforts to integrate WebAssembly-based implementations in the next year. I feel that we can retire "Source WebAssembly" if it causes maintenance issues. @btzy any views on this?
If there's nobody around who is able and willing to maintain Sourceror then it would have to be retired at some point. Also because there's virtually nobody using it, there isn't really much motivation for anyone to keep it up to date. Are the "efforts to integrate WebAssembly-based implementations" actually going to bring something better?
Because Sourceror is not part of js-slang, the pre-processing step which handles imports & exports does not work with Sourceror. This means that the WebAssembly variants of Source do not support multi-file programs currently. Instead, only the entrypoint file is passed to Sourceror currently:
frontend/src/commons/sagas/WorkspaceSaga.ts
Lines 1035 to 1060 in f2b05b2
The text was updated successfully, but these errors were encountered: