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
Currently, the import mechanism operates on dialects.
One could imagine a more modular style of files with a file-based import.
.import name // imports dialect name.import name/abc // import abc.thorin from the dialect provided files.import path/abc // imports path/abc.thorin from a local file
Local imports would allows for standard definitions like
Dialect imports would allow for a more readable and modular approach to dialect definitions.
One example would be the differentiated constructs of autodiff.
The text was updated successfully, but these errors were encountered:
While #185 fixes the underlying problem, I'll keep this one open until we have worked out a proper solution who we want to deal with imports and scoping.
Currently, the import mechanism operates on dialects.
One could imagine a more modular style of files with a file-based import.
Local imports would allows for standard definitions like
Dialect imports would allow for a more readable and modular approach to dialect definitions.
One example would be the differentiated constructs of
autodiff
.The text was updated successfully, but these errors were encountered: