Editorial: Correct ExportEntry.[[LocalName]] description

[ghost]

ExportEntry.[[LocalName]] calls itself the name used in the importing module. I think this is meant to say exporting.

https://tc39.es/ecma262/multipage/ecmascript-language-scripts-and-modules.html#table-exportentry-records

The name that is used to locally access the exported value from within the importing module. null if the exported value is not locally accessible from within the module.

Some export declarations relay imports (which would make this the importing module), but not all. It's always the exporting module for every export.

I think this probably snuck in by analogy with the ImportEntry.[[LocalName]] description.

https://tc39.es/ecma262/multipage/ecmascript-language-scripts-and-modules.html#table-importentry-record-fields

The name that is used to locally access the imported value from within the importing module.

This patch changes "importing" to "exporting" in ExportEntry.[[LocalName]].

[michaelficarra]

This is fine. It would be nice to also explain "*default*" here. Even nicer to replace it with a spec enum.

[bakkot]

"*default*" cannot be changed to a spec enum; see discussion in #2566.

It already has a detailed explanation here.

[michaelficarra]

@bakkot I think in this position, it can be replaced, but it wouldn't totally eliminate the use of "*default*".

[bakkot]

LGTM, thanks. I'm betting this is a copy-paste error from the ImportEntry Record table.

[bakkot]

@michaelficarra This is the only position which uses *default*. It can't be eliminated without either adding a special case throughout the linkage machinery or making scopes support non-string binding names, neither of which seems like a good idea. The description in #2566 is pretty thorough about this.