- 필수 기능
- 시작하기
- 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: go-best-practices/get-return
Language: Go
Severity: Notice
Category: Best Practices
In programming, it is a common convention to prefix functions with “get” when they are intended to retrieve or fetch some data or state from an object or system. When following this convention, it is generally expected that functions prefixed with “get” should return a value rather than modifying the state directly. This practice offers a number of benefits:
By adhering to the practice of having “get” functions return a value, you improve code clarity, maintain good encapsulation, promote immutability, and allow for future adaptability and extensibility. Following this convention makes the codebase more intuitive, predictable, and maintainable.
func GetSomething() {
}
func getSomethingElse() {
}
func GetSomething() int {
}
func getSomethingElse() (type1, type2){
}