| Description |
This is an enhancement of #1692.
Unnamed modules can't be added to the system modules list (because they have no name to index them by). Since they can't go in the list, they shouldn't export to the system runtime library (lib). As of alpha 108, the way this problem is dealt with is to trigger an error.
A better way to deal with these is to pretend that they were imported with IMPORT/no-lib (don't add them to the module list or import to lib), and that they were declared as private modules (see #1692). If done right, this should make them exportable to their calling module/script, and unique to it. There is no way that the modules can be reused through the module list without a name, so they won't be reused at all.
This will make simple module hierarchies easier to implement, and allow some advanced tricks that we don't need to go into here.
|
