- 필수 기능
- 시작하기
- 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/guard-let-shorthand
Language: Unknown
Severity: Warning
Category: Code Style
This rule identifies and flags redundant identifiers in optional binding within guard
statements, such as guard let name = name else { ... }
. In Swift, when the identifier on the left side of the binding is the same as the optional being unwrapped, you can omit the explicit assignment and write guard let name else { ... }
instead. This simplification improves code readability by reducing unnecessary repetition.
To comply with this rule, simply omit the explicit assignment when unwrapping an optional with the same identifier, using guard let variable else { ... }
rather than guard let variable = variable else { ... }
. Always prefer this concise form unless you need to bind to a different variable name or perform type casting.
Swift
version: 5.7guard let name = name else {
// ...
}
guard let self = self else {
// ...
}
guard interactionEnabled,
let userTapLocation = userTapLocation else {
// ...
}
guard let user = user,
var device = device else {
// ...
}
guard let name else {
// ...
}
guard let name = user?.name else {
// ...
}
guard let user = user as? User else {
// ...
}
guard var user = currentUser() else {
// ...
}