As for bounds checks (and other traps) they're all checked at runtime, no reliance on OS protections. This has a runtime cost, the reduction of which was a foc

As for bounds checks (and other traps) they're all checked at runtime, no reliance on OS protections. This has a runtime cost, the reduction of which was a focus of the last release: https://github.com/tetratelabs/wazero/releases/tag/v1.2.1 https://github.com/tetratelabs/wazero/releases/tag/v1.2.1 The optimizing compiler should also help here (with bounds checks elimination, and elision of some other checks, like divide-by-zero).