- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
ID: csharp-best-practices/base-equals
Language: C#
Severity: Error
Category: Best Practices
Using base.Equals
can be dangerous when the base is not an object
because the new base class can override Equals
, leading to unexpected behavior. This rule prevents the use of base.Equals
in a class where the base is not an object
.
class NonCompliant : Compliant
{
private int bar;
public override bool Equals(object other)
{
bool eq1;
eq1 = base.Equals(other);
var eq2 = base.Equals(other);
if (base.Equals(other))
{
return true;
}
return this.bar == ((NonCompliant)other).bar;
}
}
class Compliant
{
private int foo;
public override bool Equals(object other)
{
if (base.Equals(other))
{
return true;
}
return this.foo == ((Compliant)other).foo;
}
}
class Compliant
{
private int foo;
public override bool Equals(object other)
{
if (base.Equals(other))
{
return true;
}
return this.foo == ((Compliant)other).foo;
}
}
|
|
For more information, please read the Code Analysis documentation
Identify code vulnerabilities directly in yourVS Code editor
Identify code vulnerabilities directly inJetBrains products