Status: IN
Multiple inheritance has a narrow legitimate niche in OO design: mixin classes providing optional, orthogonal functionality (serialization, observable behavior) via statically-composed combinations — bounded by Bridge's demonstration that MI cannot deliver runtime flexibility, and by the GoF's general composition preference, constraining MI to cases where functionality is truly optional, combination is static, and no runtime variation is needed.
Three premises about multiple inheritance converge on a narrow legitimate niche defined by optional/static/non-varying constraints
Depends on (SL): gof-mixin-class-definition, mixin-class-optional-functionality-via-mi, bridge-cannot-use-multiple-inheritance-cpp