You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes modules can get quite big, and it makes sense to separate them. Sometimes modules can just be bundles of other modules.
In my case the UI module handles many different things, and keeping it all in one file is pretty inconvenient.
The idea is that you are able to "load" a module into the module itself. This essentially puts the loaded modules to the root (the module that loads) modules namespace. This is preferably not a text substitution to retain compatibility between bundle included and standalone modules.
load (
"ui_core.um"; "ui_windows.um"; "ui_widgets.um"; "ui_rectcut.um" // et cetera
)
This also relates to #173 because this would essentially solve the problem by allowing you to wrap the conflicting modules into a bundle. (Mind you, this feature is just another feature in the bucket of ideas, these problems can be addressed one way or another)
The text was updated successfully, but these errors were encountered:
@skejeton I think it will be difficult for a user to distinguish between load and import clauses. Moreover, the file system already provides a nice bundling mechanism -- folders. So I would rather consider something like import "ui/*".
Sometimes modules can get quite big, and it makes sense to separate them. Sometimes modules can just be bundles of other modules.
In my case the UI module handles many different things, and keeping it all in one file is pretty inconvenient.
The idea is that you are able to "load" a module into the module itself. This essentially puts the loaded modules to the root (the module that loads) modules namespace. This is preferably not a text substitution to retain compatibility between bundle included and standalone modules.
This also relates to #173 because this would essentially solve the problem by allowing you to wrap the conflicting modules into a bundle. (Mind you, this feature is just another feature in the bucket of ideas, these problems can be addressed one way or another)
The text was updated successfully, but these errors were encountered: