-
-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emit WASM #3897
Emit WASM #3897
Conversation
Thanks @Quafadas!
|
The documentation has been written somewhat blindly - I can't seem to get past this locally.
|
@Quafadas Could be you have a sparse git checkout. You can use |
@lefou Thankyou! I think the docs works as I expect... |
Pending further feedback and making CI happy, I believe this now to be mergeable. |
Looks good to me, thanks @Quafadas! Email me your international bank transfer details and I will close out the bounty |
@lihaoyi r.e. bounty I'd say don't worry about it I get plenty out of mill so let's keep that resource inside the project. You can either add it to the scala 3 migration slush fund, or if you ever get the chance to have dinner with Tobias and/or Lorenzo - make it a nice one. |
@Quafadas got it! In that case I'll pass the bounty to the scala center then to support their work |
Seeks to address #3837
I have some outstanding questions;
emitWasm
. sjrd pretty clearly called the linker APIwithExperimentalUseWebAssembly
. However, if at some point it became non-experimental, I assume that's a compatibility problem. Advice welcomed - I've gone with the simplest name possible -emitWasm
.Those are the two points where I'd welcome advice. I think this is the path to victory;