Suppose a class/object representing a Mininess component is in a separate file from where it is used. The compiler needs to know the nesT module type of that component in order to check the usage. Currently it is necessary for the file containing the component and the file containing the usage to be compiled in the same session and in the right order (the component must be compiled first). This is more restrictive than normal Scala rules and requires unnatural renaming of files to work properly with certain build systems, such as ant.
The behavior may have something to do with the Scala compiler's two pass type checking algorithm. Current nesT module types are handled during the first pass but perhaps that is too early. It may be necessary to do nesT module type processing during the second pass when, perhaps, more complete information about the program is available.
Suppose a class/object representing a Mininess component is in a separate file from where it is used. The compiler needs to know the nesT module type of that component in order to check the usage. Currently it is necessary for the file containing the component and the file containing the usage to be compiled in the same session and in the right order (the component must be compiled first). This is more restrictive than normal Scala rules and requires unnatural renaming of files to work properly with certain build systems, such as
ant.The behavior may have something to do with the Scala compiler's two pass type checking algorithm. Current nesT module types are handled during the first pass but perhaps that is too early. It may be necessary to do nesT module type processing during the second pass when, perhaps, more complete information about the program is available.