This product is not supported for your selected Datadog site. ().
이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다. 현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.
Metadata
ID:ruby-best-practices/reverse-each
Language: Ruby
Severity: Notice
Category: Best Practices
Description
The rule “Prefer using reverse_each” is based on the principle of optimizing your Ruby code for better performance. In Ruby, there are two main methods for iterating over the elements of an array in reverse order: reverse.each and reverse_each. While the functionality of these two methods is the same, their performance characteristics are different.
The reverse.each method creates a new array that is the reverse of the original before performing the iteration. This can lead to unnecessary memory usage, especially for large arrays, and slow down the performance of your code.
On the other hand, the reverse_each method does not create a new array. Instead, it starts from the end of the original array and works its way to the beginning, saving memory and enhancing performance.
Therefore, to adhere to good coding practices and ensure optimal performance, it is recommended to use reverse_each instead of reverse.each when you need to iterate over the elements of an array in reverse order.
Non-Compliant Code Examples
array.reverse.each{}["foo","bar"].reverse.each{}
Compliant Code Examples
array.reverse_each{}["foo","bar"].reverse_each{}
원활한 통합. Datadog Code Security를 경험해 보세요
Datadog Code Security
이 규칙을 사용해 Datadog Code Security로 코드를 분석하세요
규칙 사용 방법
1
2
rulesets:- ruby-best-practices # Rules to enforce Ruby best practices.
리포지토리 루트에 위의 내용을 포함하는 static-analysis.datadog.yml을 만듭니다
무료 IDE 플러그인을 사용하거나 CI 파이프라인에 Code Security 검사를 추가합니다