-
Notifications
You must be signed in to change notification settings - Fork 80
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
Debug builds should work on wasm32-unknown-unknown now #78
Comments
Any updates on the status of this issue? (The new link is rustwasm/team#1.) EDIT: Just noticed #83, looks like there's something a bit more complicated going on than just the above issue. |
@Kwarrtz It's in-progress. I need to switch the |
I haven't looked too closely yet, but it seems like procedural macros were fully stabilized in Rust |
don't really know that much about custom sections in wasm, can I still somehow help with the |
@ForsakenHarmony I stared to work on this already, however it's currently on the backburner. I haven't yet started on converting the That is, we need a procedural macro which will take this: js!(
console.log( 123, @{variable} );
); and emit something like this (not exactly, as the __js_raw_asm!( r#"console.log( 123, $0 );"#, variable ); Basically, the procedural macro has to take its input (the JS code), stringify it replacing every If you have some free time and feel like helping out then you could try your hand at writing such a basic procedural macro (it doesn't have to be actually functional; I can take it from there). |
Rather than chopping off the And then you could do some validation on the AST to ensure that the block expression only contains a single expression inside of it (and no statements). Alternatively, you could actually allow for statements + multiple expressions inside of js!(
var x = @{
let y = 10;
y + 20
};
); |
@Pauan Yep! Good point. As long as it stringifies the code just as the current |
ok I'll try to work on this |
initial version is in koute/stdweb#285 |
https://github.com/rust-lang-nursery/rust-wasm/issues/1
Hopefully this means cargo-web doesn't need to force release mode anymore.
The text was updated successfully, but these errors were encountered: