Can composition and inheritance be called a pattern?

Question

OOP

Hello, tell me plz, if they ask me what patterns I know, can I answer Composition and inheritance or are they not patterns?

Answer 1

A pattern is a rather utilitarian thing, a certain clear sequence or description of connections so that one or another instrument can be repeated, easily identified and conveyed.
Composition is an abstract concept that classifies what needs to be built in some other way than inheritance. Delegate and arrange so that polymorphism manifests itself through a number of objects that are not related in the inheritance chain.
Inheritance is about the fact that objects inherit an interface / state, there is no interaction scheme here, it is quite direct: A inherited from B and that's it. But there is a lot hidden inside.

Answer 2

These are not patterns. Here are the patterns: Guardian, Visitor, Opportunist, Substitute, Loner, Builder, Planner, Observer, etc.
But it's better, of course, to know and apply composition and inheritance than to spend time on a code reference.