From a68501cebda6fa1ac6affe020496d4c7575deda6 Mon Sep 17 00:00:00 2001 From: Mio Date: Tue, 31 Jan 2023 13:23:47 +0800 Subject: [PATCH] fix redundant typo --- docs/internals/optimizer.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/internals/optimizer.rst b/docs/internals/optimizer.rst index 11f55e0e3..99589db99 100644 --- a/docs/internals/optimizer.rst +++ b/docs/internals/optimizer.rst @@ -1162,7 +1162,7 @@ will be transformed into the code below after the Unused Store Eliminator step i For memory store operations, things are generally simpler, at least in the outermost yul block as all such statements will be removed if they are never read from in any code path. At function analysis level, however, the approach is similar to ``sstore``, as we do not know whether the memory location will -be read once we leave the function's scope, so the statement will be removed only if all code code paths lead to a memory overwrite. +be read once we leave the function's scope, so the statement will be removed only if all code paths lead to a memory overwrite. Best run in SSA form.