Though I'll note that (AFAIK) WASM environments don't expose access to uninitialized memory. When you grow your Memory object the new space is zeroed, and when you allocate it initially it's zeroed. This can actually show up in profilers when you examine application startup time.

loader_uninitialized would hopefully address the zeroes in the module at least...