When working on #3890 I realized that the explanation of package.order only speaks of the ordering of classes and constants, but there is no restriction on the class specialization of the class defined in package.mo. (The only requirement I can see on the class defined in package.mo is that it must have a long class definition in case there are additional files or directories providing more children to the class.)
Since it would be such a mess to define what package.order means for a non-package, can't we just add the restriction that the class in package.mo must be a package when package.order is present?
When working on #3890 I realized that the explanation of package.order only speaks of the ordering of classes and constants, but there is no restriction on the class specialization of the class defined in package.mo. (The only requirement I can see on the class defined in package.mo is that it must have a long class definition in case there are additional files or directories providing more children to the class.)
Since it would be such a mess to define what package.order means for a non-package, can't we just add the restriction that the class in package.mo must be a package when package.order is present?