Ingvar Stepanyan

> You seem to be contradicting your self here because `emscripten_exit_with_live_runtime` is the same as `emscripten_runtime_keepalive_push` + `unwind` so, if we define `emscripten_runtime_keepalive_push` as keeping node alive we would also...

To be clear, I'm not advocating that zombie processes are fine in general, and definitely don't want to revert changes that got us to native platform parity by default (when...

> Or are you saying that only extend "aliveness" to pthreads, not to the whole node event loop? That seems like a safer change for sure. Not sure tbh. I...

> Or do you think the proxying API should effectively do that automatically? Yeah, I believe it should. Otherwise we'd also need to also add `unset_strongref`, users would need to...

> I think the shuffle pattern has to be a const value on x86 Yeah, IIRC stdlib intrinsics solve this by taking such params (in shuffle and other ops with...

Oh, the name is misleading, I meant for it to just return slice. I should have called it `as_slice`. Proper arrays would be nice too, but I agree not feasible...

> I can't make a promise that I would be able to get to adding these in a moment Kind of the same, it should be a very simple fix...

It should be fairly straightforward, but do give us a shout if you get stuck.

> are these two things worth distinguishing: the header was never sent, versus it was sent with an empty value I'd say it's really up to specific header implementation and/or...

> Alternatively, it could be useful to make `Error` an enum and then have a single method with `Result` signature. Then consumer will always easily get a header value where...