Ingvar Stepanyan

@tlively Ah, I've missed that nuance. From looking at implementation, it seems that the primary difference is in layout of aggregate parameters / results (structs by value and such)? That's...

@TheBlueMatt Thanks for linking to that discussion, very interesting. I hope the wasm-bindgen changes @devsnek is working on will work out and we'll get C ABI fixed for wasm32-unknown-unknown without...

> With Node, we would have to write bindings by hand. I don't think this is necessarily true. Node.js TypeScript definitions are pretty precise, and there is already `wasm-bindgen-typescript` that...

> With native Rust you get to use the same types and algorithms on both the server and client (using serde to send data back and forth). So unlike the...

@xtuc Yes, thanks, I saw that issue and that's what I referred to in > aside from ESM integration in the description (and that's also the reason I sent these...

> I don't think your input/output are for the same file, using the input file in the link you gisted above I get: Sorry, I'm not sure what you meant...

I also wonder if it would be possible to have this reordering as an optional pass, so that by default functions would appear in original order and roundtrip would be...

@fitzgen As far as I understand from the code, functions should be already naturally added in original order to the arena during parsing, and that order is preserved throughout most...

> doesn't look like it has a data section, but the data section is there (and is the same size in both) Oh yeah, sorry, as I said, it was...

I experimented with this a bit, and, while disabling function reordering decreases size a bit closer to original, it seems that the main overhead remains and is caused by locals...