From ab3e577da8840417776d2d8417951692960a2dbf Mon Sep 17 00:00:00 2001 From: Michael Ficarra Date: Sun, 4 Feb 2024 22:07:25 -0800 Subject: [PATCH 1/2] Meta: update ecmarkup (#3277) --- package-lock.json | 14 +++++++------- package.json | 2 +- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/package-lock.json b/package-lock.json index 892a6fc73c..5dceaad343 100644 --- a/package-lock.json +++ b/package-lock.json @@ -9,7 +9,7 @@ "version": "1.0.0", "license": "SEE LICENSE IN https://tc39.es/ecma262/#sec-copyright-and-software-license", "dependencies": { - "ecmarkup": "^18.1.0" + "ecmarkup": "^18.1.3" }, "devDependencies": { "glob": "^7.1.6", @@ -724,9 +724,9 @@ } }, "node_modules/ecmarkup": { - "version": "18.1.0", - "resolved": "https://registry.npmjs.org/ecmarkup/-/ecmarkup-18.1.0.tgz", - "integrity": "sha512-0ngQ2YYizUkswKZcCn8g8BlCoaEAN8R2DOZfupk0k2lnIWzUZJNxjld4lt97YTJxcZxVTMERmukZ8svBSz9UcQ==", + "version": "18.1.3", + "resolved": "https://registry.npmjs.org/ecmarkup/-/ecmarkup-18.1.3.tgz", + "integrity": "sha512-grvHr/9NlFnOJQ9rL2+AlD1Q/IGT4siTdl1nsSi6gZVrOxIma6sBR9WStlr9s2TxtKXx7ouM18HsZ+RF9OJlHA==", "dependencies": { "chalk": "^4.1.2", "command-line-args": "^5.2.0", @@ -2940,9 +2940,9 @@ } }, "ecmarkup": { - "version": "18.1.0", - "resolved": "https://registry.npmjs.org/ecmarkup/-/ecmarkup-18.1.0.tgz", - "integrity": "sha512-0ngQ2YYizUkswKZcCn8g8BlCoaEAN8R2DOZfupk0k2lnIWzUZJNxjld4lt97YTJxcZxVTMERmukZ8svBSz9UcQ==", + "version": "18.1.3", + "resolved": "https://registry.npmjs.org/ecmarkup/-/ecmarkup-18.1.3.tgz", + "integrity": "sha512-grvHr/9NlFnOJQ9rL2+AlD1Q/IGT4siTdl1nsSi6gZVrOxIma6sBR9WStlr9s2TxtKXx7ouM18HsZ+RF9OJlHA==", "requires": { "chalk": "^4.1.2", "command-line-args": "^5.2.0", diff --git a/package.json b/package.json index e9aad18e15..5b4aa5d191 100644 --- a/package.json +++ b/package.json @@ -23,7 +23,7 @@ "license": "SEE LICENSE IN https://tc39.es/ecma262/#sec-copyright-and-software-license", "homepage": "https://tc39.es/ecma262/", "dependencies": { - "ecmarkup": "^18.1.0" + "ecmarkup": "^18.1.3" }, "devDependencies": { "glob": "^7.1.6", From 3a773fc9fae58be023228b13dbbd402ac18eeb6b Mon Sep 17 00:00:00 2001 From: Michael Ficarra Date: Sun, 4 Feb 2024 22:07:29 -0800 Subject: [PATCH 2/2] Editorial: pull in ecmarkup reduced-width document styles (#3277) --- spec.html | 32 +++++++++++--------------------- 1 file changed, 11 insertions(+), 21 deletions(-) diff --git a/spec.html b/spec.html index 5ea77b7400..8faa49c00c 100644 --- a/spec.html +++ b/spec.html @@ -40,16 +40,6 @@ width: 100%; font-size: 80%; } - - .module-overflow { - overflow-y: scroll; - display: block; - } - - .module-overflow-note { - overflow-y: scroll; - } - 
   title: ECMAScript® 2024 Language Specification
@@ -27020,7 +27010,7 @@ 
Example Cyclic Module Record Graphs

 
           
Calling _A_.Evaluate() calls InnerModuleEvaluation on _A_, _B_, and _D_, which all transition to ~evaluating~. Then InnerModuleEvaluation is called on _A_ again, which is a no-op because it is already ~evaluating~. At this point, _D_.[[PendingAsyncDependencies]] is 0, so ExecuteAsyncModule(_D_) is called and we call _D_.ExecuteModule with a new PromiseCapability tracking the asynchronous execution of _D_. We unwind back to the InnerModuleEvaluation on _B_, setting _B_.[[PendingAsyncDependencies]] to 1 and _B_.[[AsyncEvaluation]] to *true*. We unwind back to the original InnerModuleEvaluation on _A_, setting _A_.[[PendingAsyncDependencies]] to 1. In the next iteration of the loop over _A_'s dependencies, we call InnerModuleEvaluation on _C_ and thus on _D_ (again a no-op) and _E_. As _E_ has no dependencies and is not part of a cycle, we call ExecuteAsyncModule(_E_) in the same manner as _D_ and _E_ is immediately removed from the stack. We unwind once more to the original InnerModuleEvaluation on _A_, setting _C_.[[AsyncEvaluation]] to *true*. Now we finish the loop over _A_'s dependencies, set _A_.[[AsyncEvaluation]] to *true*, and remove the entire strongly connected component from the stack, transitioning all of the modules to ~evaluating-async~ at once. At this point, the fields of the modules are as given in .

 
-          
+          
             
@@ -27083,7 +27073,7 @@ 
Example Cyclic Module Record Graphs
Let us assume that _E_ finishes executing first. When that happens, AsyncModuleExecutionFulfilled is called, _E_.[[Status]] is set to ~evaluated~ and _C_.[[PendingAsyncDependencies]] is decremented to become 1. The fields of the updated modules are as given in .

 
-          
+          
             

               
                 

 
           

@@ -27119,7 +27109,7 @@ 
Example Cyclic Module Record Graphs
_D_ is next to finish (as it was the only module that was still executing). When that happens, AsyncModuleExecutionFulfilled is called again and _D_.[[Status]] is set to ~evaluated~. Then _B_.[[PendingAsyncDependencies]] is decremented to become 0, ExecuteAsyncModule is called on _B_, and it starts executing. _C_.[[PendingAsyncDependencies]] is also decremented to become 0, and _C_ starts executing (potentially in parallel to _B_ if _B_ contains an `await`). The fields of the updated modules are as given in .

 
-          
+          
             

               
                 

 
           

@@ -27164,7 +27154,7 @@ 
Example Cyclic Module Record Graphs
Let us assume that _C_ finishes executing next. When that happens, AsyncModuleExecutionFulfilled is called again, _C_.[[Status]] is set to ~evaluated~ and _A_.[[PendingAsyncDependencies]] is decremented to become 1. The fields of the updated modules are as given in .

 
-          
+          
             

               
                 

 
           

@@ -27200,7 +27190,7 @@ 
Example Cyclic Module Record Graphs
Then, _B_ finishes executing. When that happens, AsyncModuleExecutionFulfilled is called again and _B_.[[Status]] is set to ~evaluated~. _A_.[[PendingAsyncDependencies]] is decremented to become 0, so ExecuteAsyncModule is called and it starts executing. The fields of the updated modules are as given in .

 
-          
+          
             

               
                 

 
           

@@ -27236,7 +27226,7 @@ 
Example Cyclic Module Record Graphs
Finally, _A_ finishes executing. When that happens, AsyncModuleExecutionFulfilled is called again and _A_.[[Status]] is set to ~evaluated~. At this point, the Promise in _A_.[[TopLevelCapability]] (which was returned from _A_.Evaluate()) is resolved, and this concludes the handling of this module graph. The fields of the updated module are as given in .

 
-          
+          
             

               
                 

 
           

@@ -27263,7 +27253,7 @@ 
Example Cyclic Module Record Graphs
Alternatively, consider a failure case where _C_ fails execution and returns an error before _B_ has finished executing. When that happens, AsyncModuleExecutionRejected is called, which sets _C_.[[Status]] to ~evaluated~ and _C_.[[EvaluationError]] to the error. It then propagates this error to all of the AsyncParentModules by performing AsyncModuleExecutionRejected on each of them. The fields of the updated modules are as given in .

 
-          
+          
             

               
                 

 
           

@@ -27302,7 +27292,7 @@ 
Example Cyclic Module Record Graphs
_A_ will be rejected with the same error as _C_ since _C_ will call AsyncModuleExecutionRejected on _A_ with _C_'s error. _A_.[[Status]] is set to ~evaluated~. At this point the Promise in _A_.[[TopLevelCapability]] (which was returned from _A_.Evaluate()) is rejected. The fields of the updated module are as given in .

 
-          
+          
             

               
                 

 
           

@@ -27331,7 +27321,7 @@ 
Example Cyclic Module Record Graphs
Then, _B_ finishes executing without an error. When that happens, AsyncModuleExecutionFulfilled is called again and _B_.[[Status]] is set to ~evaluated~. GatherAvailableAncestors is called on _B_. However, _A_.[[CycleRoot]] is _A_ which has an evaluation error, so it will not be added to the returned _sortedExecList_ and AsyncModuleExecutionFulfilled will return without further processing. Any future importer of _B_ will resolve the rejection of _B_.[[CycleRoot]].[[EvaluationError]] from the evaluation error from _C_ that was set on the cycle root _A_. The fields of the updated modules are as given in .

 
-          
+          
             

               
                 

 
           

@@ -27519,7 +27509,7 @@ 
Source Text Module Records

               
                 

             

           

         
-        
+        
           
 gives examples of ImportEntry records fields used to represent the syntactic import forms:

           
             
@@ -27664,7 +27654,7 @@ 
Source Text Module Records

             
           

         
-        
+        
           
 gives examples of the ExportEntry record fields used to represent the syntactic export forms: