Ingvar Stepanyan

@sebmarkbage Huh, you're right. Everything inside of the `do` expression, incl. `{x:1}` is a block. Might be a serious issue for us.

@syranide I still fail to see why you compare arrow functions to do expressions. They were designed as functions after all, so they had to be able to provide code...

I got a feature request in https://github.com/GoogleChromeLabs/wasi-fs-access/issues/2 to use the current working directory functionality. In general, https://github.com/WebAssembly/wasi-libc/pull/214/files looks promising, but my understanding is that the current directory emulation is purely...

> However reading the current working directory back out of a child process I don't think is needed for POSIX-like environments. I guess that's fair, if we consider only POSIX-like...

You mentioned this yourself, above, but just to resurface - maybe wasi-libc could read `PWD` from environment table upon startup and chdir to that (or keep `/` if `PWD` is...

> Alternatively perhaps we could add new preopen type. Right now we only have one: __WASI_PREOPENTYPE_DIR. We could perhaps add __WASI_PREOPENTYPE_PWD? That could work nicely, yeah, and we could even...

Should we reopen this issue for tracking & discussion for now?

> because the libc's have numerous differences which would lead to silent breakage I know there are some historical differences between filesystem constants, but otherwise they both use musl and...

That's a risk, yes, and, yes, secretly I'd hope someday Emscripten could actually be compatible with wasi-libc when in STANDALONE_WASM mode, but in this particular project I'm doing so much...

@jhoneill That's pretty amazing, thanks. Maybe it would be possible to somehow ship this as a PowerShell module so that it could be installed via PSGet?