You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I guess the main thought is that tags, and certain class attributes will get overwritten depending on the sequence of the inheritance?
In general though, our Mixin classes are relatively "mutually exclusive" right?
This would only be an issue if for some reason, someone inherited first from Mixin, and then BaseEstimator, or some other Base*, where some attributes/tags get overwritten?
Yeah the main concern is BaseEstimator needing to be the last one of our mixins in MRO. I'll write up a test, that should make it clear, and if we need to add more constraints, we can do that
xref: #30227 (review)
We should make sure it goes the right way, so that tags are set correctly, and to avoid other potential issues.
The text was updated successfully, but these errors were encountered: