Closed caridy closed 9 years ago
I believe this refers to circular references in the bindings setup. The point is I can't do:
a.js
export {a} from './b.js';
b.js
export {a} from './a.js';
So we stop circularity of bindings, not circularity of modules.
@guybedford is right: this part of the semantics treats re-export cycles as a static error, not cyclic module dependencies. Re-export cycles are nonsense: in the example above, a
is not actually defined anywhere.
Reported by @bmeck (https://github.com/WebAssembly/design/issues/256#issuecomment-120558466)