1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DOC] Stop discouraging the use of Array#each (#10119)

Browse Source
This commit is contained in:
Takashi Kokubun 2024-02-27 14:02:24 -08:00 committed by GitHub
parent edc7b73fc4
commit 3668118572
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/yjit/yjit.md
View File

@ -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 classes that wrap objects if you can
- Avoid methods that just call another method, trivial one-liner methods - 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 - 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. - 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. 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.