Ingvar Stepanyan
Ingvar Stepanyan
Just allowing to somehow set target to WASI would be already good. Right now playing with porting some libraries to WASM via wasm-pack, but running into runtime panics due to...
@yurydelendik Looks like the linked issue has been resolved since.
Yeah, and seems like at this point it would be a fairly simple fix to allow other targets.
@Pauan > I think this needs to be added to wasm-bindgen first before it can be added to wasm-pack. Does wasm-bindgen differentiate or, indeed, even know, which target Wasm was...
> For WASI it is necessary to pass in the WASI functions, but wasm-bindgen doesn't do this, therefore `wasm32-wasi` won't work. Ah yeah, that's a good point, these imports would...
There is no need to commit to any specific implementation for WASI syscalls, the JS wrapper would simply need to propagate the imports and let Webpack config or whatever handle...
> especially when those cleanups are non-trivial Hm, it feels like the opposite - because those cleanups are non-trivial, they're quite hard to model via refactor command (unless I'm missing...
UPD: Alon Zakai pointed me to a PR in Relooper back in 2016 that improved cases like this: https://github.com/WebAssembly/binaryen/pull/648 Quotes: > In particular, the old Relooper used to add "label"...
Ping - any thoughts on the above? In particular, are there any plans to update the Relooper algorithm to match upstream improvements?
Ok, fair enough. I don't have capacity to work on this currently either, but I'll rename the issue and leave it open as well.