A prerequisite to this is probably adding module expressions. Maybe not.
An @import("./url") is equivilent to inlining a module expression with that file's content. The string can be dynamic.
To be clear this issue will be just for local files. A separate proposal will be opened detailing how remote URLs will resolve, and more importantly the plan for how remote dependencies will be managed.
Milestone: 0.2.0.
An @import("./url") is equivilent to inlining a module expression with that file's content. The string can be dynamic.
Surely not. What about files that reference each other?
What about files that reference each other?
Deduplicate. I guess I should've been more careful with my words "inlining [...] with that file's content". Two files can 100% reference each other, though what comes into question is how top-level side effects are to be handled.