3 ms·

I guess I don't entirely agree, but I do wonder why each import has to include 'gleam' in the path. Why can't it assume that the default path is 'gleam' and imp

I guess I don't entirely agree, but I do wonder why each import has to include 'gleam' in the path. Why can't it assume that the default path is 'gleam' and import libraries relative to that path. Like `import string` instead of having to do `import gleam/string`?

lpil 2y ago
It's the namespace that belongs to the core team. It couldn't be just `string` etc as that would collide with existing Erlang modules. Other Gleam libraries will use other namespaces.