From 45bce90a8ba3c26aa83427a77328a855c9e2e1d8 Mon Sep 17 00:00:00 2001 From: George Padron Date: Thu, 17 Apr 2025 00:33:14 -0500 Subject: [PATCH] Fix typo: outweight -> outweigh --- compiler/docs/DESIGN_GOALS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compiler/docs/DESIGN_GOALS.md b/compiler/docs/DESIGN_GOALS.md index 76d19e25c08..ef619db4770 100644 --- a/compiler/docs/DESIGN_GOALS.md +++ b/compiler/docs/DESIGN_GOALS.md @@ -19,7 +19,7 @@ The idea of React Compiler is to allow developers to use React's familiar declar The following are explicitly *not* goals for React Compiler: * Provide perfectly optimal re-rendering with zero unnecessary recomputation. This is a non-goal for several reasons: - * The runtime overhead of the extra tracking involved can outweight the cost of recomputation in many cases. + * The runtime overhead of the extra tracking involved can outweigh the cost of recomputation in many cases. * In cases with conditional dependencies it may not be possible to avoid recomputing some/all instructions. * The amount of code may regress startup times, which would conflict with our goal of neutral startup performance. * Support code that violates React's rules. React's rules exist to help developers build robust, scalable applications and form a contract that allows us to continue improving React without breaking applications. React Compiler depends on these rules to safely transform code, and violations of rules will therefore break React Compiler's optimizations.