- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`ID: swift-code-style/collection-size
Language: Unknown
Severity: Notice
Category: Best Practices
This rule identifies conditions where a collection’s size is compared in a way that will always evaluate to true or false, such as checking if count < 0
or count >= 0
. Since collection counts are never negative, these comparisons are logically incorrect and indicate a potential flaw or misunderstanding in the code.
To avoid violations of this rule, ensure that comparisons involving collection sizes use valid and meaningful operators. For example, use count == 0
to check if a collection is empty, or count > 0
to verify it contains elements. Reviewing the logic behind size comparisons helps maintain correct and readable code.
if (something.count < 0) {
// some statement
}
if (something.count >= 0) {
// some statement
}
if (something.count == 0) {
// some statement
}
if (something.count > 0) {
// some statement
}