From 3668118572c8d1f8faa95034883b52aa9d05c5c4 Mon Sep 17 00:00:00 2001 From: Takashi Kokubun Date: Tue, 27 Feb 2024 14:02:24 -0800 Subject: [PATCH] [DOC] Stop discouraging the use of Array#each (#10119) --- doc/yjit/yjit.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/doc/yjit/yjit.md b/doc/yjit/yjit.md index 63588c2869..8aab1aed22 100644 --- a/doc/yjit/yjit.md +++ b/doc/yjit/yjit.md @@ -268,8 +268,6 @@ This section contains tips on writing Ruby code that will run as fast as possibl - Avoid classes that wrap objects if you can - Avoid methods that just call another method, trivial one-liner methods - Try to write code so that the same variables always have the same type -- Use `while` loops if you can, instead of C methods like `Array#each` - - This is not idiomatic Ruby, but could help in hot methods - CRuby method calls are costly. Avoid things such as methods that only return a value from a hash or return a constant. You can also use the `--yjit-stats` command-line option to see which bytecodes cause YJIT to exit, and refactor your code to avoid using these instructions in the hottest methods of your code.