This product is not supported for your selected Datadog site. ().
이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다. 현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.
Metadata
ID:go-best-practices/comparison-true
Language: Go
Severity: Notice
Category: Best Practices
Description
In Go, it is recommended to use the if foo syntax, where foo is a boolean expression, rather than comparing it explicitly to true using if foo == true.
Here are the reasons why if foo is preferred:
Simplicity and Readability: Using if foo reduces unnecessary verbosity and improves code readability. It directly expresses the condition based on the truthiness of foo, making it easier to understand the intent of the condition without the need for an explicit comparison.
Idiomatic Expression: In Go, boolean expressions like foo already evaluate to true or false, so comparing them explicitly to true is redundant and unnecessary.
Avoiding Errors: Using if foo helps prevent common mistakes, such as accidentally using = (assignment operator) instead of == (equality operator) in the comparison, which would lead to a logical error.
For example, consider the following code snippets:
123iffoo{// Code block}
123iffoo==true{// Code block}
Both snippets achieve the same result if foo evaluates to true. However, the first snippet using if foo is preferred for its simplicity, clarity, and adherence to Go’s idiomatic style.
By using if foo instead of if foo == true, you can write cleaner and more readable code that takes advantage of the natural boolean evaluation in Go.
Non-Compliant Code Examples
funcmain(){iffoo==true{}}
Compliant Code Examples
funcmain(){iffoo{}}
원활한 통합. Datadog Code Security를 경험해 보세요
Datadog Code Security
이 규칙을 사용해 Datadog Code Security로 코드를 분석하세요
규칙 사용 방법
1
2
rulesets:- go-best-practices # Rules to enforce Go best practices.
리포지토리 루트에 위의 내용을 포함하는 static-analysis.datadog.yml을 만듭니다
무료 IDE 플러그인을 사용하거나 CI 파이프라인에 Code Security 검사를 추가합니다