From cacc7bf5f0cc4b18f81809b2d61862f0224259d4 Mon Sep 17 00:00:00 2001 From: Yuki Okushi <jtitor@2k36.org> Date: Wed, 31 Aug 2022 22:27:37 +0900 Subject: [PATCH] Fix a typo on `wasm64-unknown-unknown` doc --- src/doc/rustc/src/platform-support/wasm64-unknown-unknown.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/doc/rustc/src/platform-support/wasm64-unknown-unknown.md b/src/doc/rustc/src/platform-support/wasm64-unknown-unknown.md index 021b904debd8f..6932e6a5764bc 100644 --- a/src/doc/rustc/src/platform-support/wasm64-unknown-unknown.md +++ b/src/doc/rustc/src/platform-support/wasm64-unknown-unknown.md @@ -30,7 +30,7 @@ is 8-bytes large as well as pointers. The tradeoff, though, is that the maximum memory size is now the full 64-bit address space instead of the 4GB as limited by the 32-bit address space for `wasm32-unknown-unknown`. -This target is not a stable target. The [memory64] WebAssembly proposal is stil +This target is not a stable target. The [memory64] WebAssembly proposal is still in-progress and not standardized. This means that there are not many engines which implement the `memory64` feature and if they do they're likely behind a flag, for example: