Shouldn't ExecuteModule use the Execution Context constructed in InitializeEnvironment?

[jmdyck]

I just noticed that 16.2.1.6.4 InitializeEnvironment and 16.2.1.6.5 ExecuteModule (for a Source Text Module Record) both have:

1. Let _moduleContext_ be a new ECMAScript code execution context.
1. Set the Function of _moduleContext_ to *null*.
1. Set the Realm of _moduleContext_ to _module_.[[Realm]].
1. Set the ScriptOrModule of _moduleContext_ to _module_.
1. Set the VariableEnvironment of _moduleContext_ to _module_.[[Environment]].
1. Set the LexicalEnvironment of _moduleContext_ to _module_.[[Environment]].

Originally, those steps were only in ExecuteModule, and then PR #1670 moved them all to InitializeEnvironment (putting the resulting _moduleContext_ into _module_.[[Context]], which was then used in ExecuteModule).

But then PR #2408 (Top Level Await) added those steps back to ExecuteModule (and dropped the reference to _module_.[[Context]]).

I'm pretty sure this was unintentional (just an ill-resolved rebase conflict), because:

• now there's no use of _module_.[[Context]], and
• between 1670 and 2408, PR Normative: Add public and private class fields, static class features, private methods & getters/setters #1668 added a PrivateEnvironment to execution contexts, so the EC constructed in InitializeEnvironment has a PrivateEnvironment, but the one constructed in ExecuteModule doesn't (or doesn't appear to).

Can someone confirm that ExecuteModule should just use _module_.[[Context]]?