No Multiple Inheritance (Only Interface-Class Contracts): Pitfalls

Pitfalls and red flags

• Trying to fake multiple inheritance with deep unrelated extends chains that break UVM intent.

• Assuming interface classes provide code bodies; they only enforce method signatures.

• Putting too much state into helpers, creating hidden coupling and hard-to-trace side effects.

• Skipping capability contracts and relying on downcasts instead of polymorphic APIs.

Related topics

• Back to No Multiple Inheritance (Only Interface-Class Contracts)