ModuleImport should not be part of effective world because it's sole
purpose is to provide String->QNameModule mapping.
Change-Id: I9cabc16b7c711edffad8ba9c9306f1fe0c5c81ec
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
* <p>
* The import statement makes definitions from one module available inside another module or submodule.
*/
* <p>
* The import statement makes definitions from one module available inside another module or submodule.
*/
+// FIXME: 3.0.0 this class is a leak of the declared world into the effective one. In effective world, all nodes form
+// a tree, which consists of multiple (mostly) QName-navigated namespaces. As such module imports contribute
+// only a prefix/QNameModule mapping to the effective world and hence should be mapped that way:
+// - Module exposes String->QNameModule mapping
public interface ModuleImport extends DocumentedNode {
/**
* Returns the name of the module to import.
public interface ModuleImport extends DocumentedNode {
/**
* Returns the name of the module to import.