Carl Mäsak

Pawel Murias points out that we can arrange things so that all modules are compiled first, and only later do we run all the compunits. This is a good point,...

One thing I realized is that all the forms of `import`, even the first form, will need to clearly specify which names they declare in the lexical scope. In the...

@vendethiel Yes, something like that is what I'd expect too. Note that the first form (`import * from m;`) precludes jumping to an actual declaration in the loaded module. Guess...

Exports should be [immutable bindings, like in ES6](http://2ality.com/2015/07/es6-module-exports.html). That post is great, I need to read it again. If I'm reading it right, the fact that exports are immutable bindings...

One thing (it seems to me) we will lose if we allow cyclic bindings is the ability to tell at parse-time what type object is in a name like `x.y.z.MyType`....

I was reading [a TC39 proposal](https://github.com/tc39/proposal-export-default-from) today, and it seems to have changed my mind about whether `export` should be a statement. In the above discussion, I have `@export` as...

Both export form 2 and export form 4 support the same type of `foo as bar` renaming syntax as does import form 2.

Just throwing [this blog post about Python imports](https://chrisyeh96.github.io/2017/08/08/definitive-guide-python-imports.html) into this issue, as it seems to have relevant information about a lot of things that we might want to consider when...

I just want to add, for sentimentality, that once it _did_ feel amazing that we had all those code examples. But 007 has basically outgrown that. The previously fantastic is...

I think two of the most realistic macro ideas to include in the examples would be #122, #152 and #203. All of those are definitely tied to real use cases.