Nick Zavaritsky

Side trace may break loop invariants, rendering loop invariant code motion performed in the parent invalid, ex: ``` lua local x = 1 for i = 1, 1000 do func(purefunc(x))...

> What do I miss? You enter a root trace with a "dirty" "immutable cdata stack", the trace doesn't touch the "special TValue" (hence not added to a snapshot). Now...

After internal discussions we decided that selecting old or new `CALL` automatically based on the server version is a bad idea after all. Client code will notice the difference in...

@devsnek > I think this seems better suited to userland. There are some technical difficulties. Please check the overview below. Personally, I don't see how this could be made into...

POC #36672

@tniessen Thank you for tuning in! > Implicit caching Implicit caching is no-go. Do `openssl speed sha256` to get the idea how high the latency for a cache hit would...

@tniessen Thank you for sharing the paper. Is it fine to circulate the link? > there are approaches to sandbox Node.js applications (without the overhead of containers)... > by default,...

One use-case for WASI is for shipping CLI tools. Imagine an existing cross-platform C++ codebase. We can ship native binary packages for various Linux-es, OS X, Windows and what else....

@sunfishcode It's great that `wasi-libc` is taking steps towards being more POSIX-compatible. I am also happy to learn that CLI tool support is considered important. While incremental approach is usually...

@bjorn3 @sunfishcode Thank you for the comments. I've been checking other threads (ex. https://github.com/WebAssembly/WASI/issues/109). My takeaway was that * WASI is fond of capabilities-based access to the filesystem; * WASI...