From 61567f4795bd3fe707ddb84ad71e028a9b82cdfe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Raymond=20Lei=28=E9=9B=B7=E8=8F=A9=E5=AE=87=29=3B=20?= =?UTF-8?q?=E4=A8=BB-Ficus=20religiosa-Cousin?= Date: Sun, 12 Oct 2025 01:57:16 -0400 Subject: [PATCH] Update README with clarification on loop unrolling Clarify the discussion on loop unrolling in the context of performance gains. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e77e366..2e4787b 100644 --- a/README.md +++ b/README.md @@ -248,7 +248,7 @@ A common guideline in programming is the **90/10 Rule** (or 80/20 Rule), which s ### 5. **Examples of Premature Optimization Pitfalls** - - **Loop Unrolling**: Manually unrolling loops in the hopes of performance gains, even when the loop is not a bottleneck. + - **Loop Unrolling**: Manually unrolling loops in the hopes of performance gains, even when the loop is not a bottleneck. <--- not yielding? - **Complex Caching Mechanisms**: Adding caching layers or memoization in parts of the code where there’s little measurable impact on runtime. - **Avoiding Abstraction**: Writing overly specific code (e.g., using inline code instead of functions) to reduce “function call overhead” when the real bottleneck lies elsewhere.