From c1b9a1241d25915a259058c2cf66d6756160efe6 Mon Sep 17 00:00:00 2001 From: John-David Dalton Date: Sun, 17 Sep 2017 22:58:28 -0700 Subject: [PATCH] =?UTF-8?q?Add=20`export=20*=20as=20ns=20from=20"mod?= =?UTF-8?q?=E2=80=9D`=20updates.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- spec.html | 88 +++++++++++++++++++++++++++++++++++-------------------- 1 file changed, 57 insertions(+), 31 deletions(-) diff --git a/spec.html b/spec.html index 66c8bd1faf..9d4f3a07cb 100644 --- a/spec.html +++ b/spec.html @@ -21962,6 +21962,23 @@

Source Text Module Records

*null* + + + `export * as ns from "mod";` + + + *null* + + + `"mod"` + + + `"*"` + + + `"ns"` + + @@ -22043,7 +22060,7 @@

ResolveExport( _exportName_, _resolveSet_ ) Concrete Method

ResolveExport attempts to resolve an imported binding to the actual defining module and local binding name. The defining module may be the module represented by the Module Record this method was invoked on or some other module that is imported by that module. The parameter _resolveSet_ is use to detect unresolved circular import/export paths. If a pair consisting of specific Module Record and _exportName_ is reached that is already in _resolveSet_, an import circularity has been encountered. Before recursively calling ResolveExport, a pair consisting of _module_ and _exportName_ is added to _resolveSet_.

If a defining module is found, a ResolvedBinding Record {[[Module]], [[BindingName]]} is returned. This record identifies the resolved binding of the originally requested export.

- +

If a defining module cannot be found (i.e. resolution fails), there are three cases.