Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
framework-3.0.0, framework-3.0.1, framework-3.0.2, framework-3.0.3, framework-3.0.4, framework-3.0.5, framework-3.0.6
-
None
Description
When calculating the package spaces for modules to check for class space consistency, the resolver algorithm incorrectly assumes that already resolved modules with substitutable exports will be handled in import calculation like they are for resolving modules, but already exported modules do not have entries in the candidate map so this fails. As a result, all substitutable exports are dropped and are not considered at all when it comes to consistency checking. We need to look at the wires to calculate exported packages for already resolved modules.