Sam Clegg
Sam Clegg
> By construction, we know that the tests will run on the very same Python setup that goes out to the end users. But this construction is very new and...
BTW I hope is that this PR will bring the emscripten CI and emscripten-releases builders closer to your CI, in that they will no longer run dev dependencies visible to...
I suppose we can land this change without removing the opt-out, and then we and continue to discuss the opt out separately.
Yes, it certainly looks like this is something that API current API explicitly does not support. @juj originally designed this API so he would be the one who might know...
Can we add some some new tests based on these?
> on behalf of wasm people I know I would like to thank @jerbob92 and @sbc100 for progressing this, as it not only unlocks things like pdfium, but also generic...
> > If you just wast a wasi version of the wabt tools I think the simplest path would be to use wasi-sdk to build it. Of course that doesn't...
(I guess maybe what you are saying is that it would be nice if the web version of wabt, which is run by emscripten, happened to also be WASI compliant.....
> @sbc100 I have done some more progress on this PR now: > > * Implemented WASI pre-opens > * Implement mkdirat > > I do have some questions though:...
> A stupid nit - if it was based on wasi libc, shouldn't there be copyright attribution somewhere? (Or is that not necessary?) No stupid at all, we should certainly...