[red-knot] Move the ClassBase
enum to its own submodule
#14957
Merged
+181
−173
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This enum is no longer an implementation detail of how we infer the MROs of classes, so it no longer feels appropriate for it to live in
mro.rs
. It's not very big right now, so we could move it intotypes.rs
. However, I think our general feeling is thattypes.rs
andinfer.rs
are both already a little too big, and I also expect this enum to continue to grow as we add support for more special forms and generics. This PR therefore moves the enum to its own submodule,class_base.rs
.Test Plan
All existing tests pass. No new ones are added; this is a pure refactor with no behavioural changes.