Merge branch 'draft-v8' into draft-v9

Author: BillWagner

…encies/EcmaTC49.BuildGrammar.2.1.0.nupkg …encies/EcmaTC49.BuildGrammar.2.4.0.nupkg.github/workflows/dependencies/EcmaTC49.BuildGrammar.2.1.0.nupkg renamed to .github/workflows/dependencies/EcmaTC49.BuildGrammar.2.4.0.nupkg .github/workflows/dependencies/EcmaTC49.BuildGrammar.2.1.0.nupkg renamed to .github/workflows/dependencies/EcmaTC49.BuildGrammar.2.4.0.nupkg

@@ -22,7 +22,7 @@ jobs:
         - 'do not merge'
     steps:
       - name: Harden Runner
-        uses: step-security/harden-runner@58077d3c7e43986b6b15fba718e8ea69e387dfcc # v2.15.1
+        uses: step-security/harden-runner@fe104658747b27e96e4f7e80cd0a94068e53901d # v2.16.1
         with:
           egress-policy: audit
 

.github/workflows/dependencies/GrammarTestingEnv.tgz

@@ -35,7 +35,7 @@ jobs:
       # Install build grammar global tool
     - name: Install BuildGrammar tool
       run: |
-        dotnet tool install --version 2.1.0 --global --add-source ./.github/workflows/dependencies/ EcmaTC49.BuildGrammar
+        dotnet tool install --version 2.4.0 --global --add-source ./.github/workflows/dependencies/ EcmaTC49.BuildGrammar
 
     - name: run validate
       run: |

.github/workflows/do-not-merge-label-check.yml

@@ -29,7 +29,7 @@ jobs:
 
     steps:
     - uses: actions/checkout@0c366fd6a839edf440554fa01a7085ccba70ac98
-    - uses: DavidAnson/markdownlint-cli2-action@07035fd053f7be764496c0f8d8f9f41f98305101 # v22.0.0
+    - uses: DavidAnson/markdownlint-cli2-action@ce4853d43830c74c1753b39f3cf40f71c2031eb9 # v23.0.0
       with:
         config: ".markdownlint-cli2.jsonc"
         globs: "standard/*.md"

.github/workflows/grammar-validator.yaml

@@ -102,6 +102,9 @@
     - [§8.3.9](types.md#839-the-bool-type)  The Bool type
     - [§8.3.10](types.md#8310-enumeration-types)  Enumeration types
     - [§8.3.11](types.md#8311-tuple-types)  Tuple types
+      - [§8.3.11.1](types.md#83111-general)  General
+      - [§8.3.11.2](types.md#83112-eliding-intermediate-tuple-creation)  Eliding intermediate tuple creation
+      - [§8.3.11.3](types.md#83113-runtime-representation)  Runtime representation
     - [§8.3.12](types.md#8312-nullable-value-types)  Nullable value types
     - [§8.3.13](types.md#8313-boxing-and-unboxing)  Boxing and unboxing
   - [§8.4](types.md#84-constructed-types)  Constructed types
@@ -175,7 +178,7 @@
       - [§9.4.4.22](variables.md#94422-general-rules-for-simple-expressions)  General rules for simple expressions
       - [§9.4.4.23](variables.md#94423-general-rules-for-expressions-with-embedded-expressions)  General rules for expressions with embedded expressions
       - [§9.4.4.24](variables.md#94424-invocation-expressions-and-object-creation-expressions)  Invocation expressions and object creation expressions
-      - [§9.4.4.25](variables.md#94425-simple-assignment-expressions)  Simple assignment expressions
+      - [§9.4.4.25](variables.md#94425-simple-and-deconstructing-assignment-expressions)  Simple and deconstructing assignment expressions
       - [§9.4.4.26](variables.md#94426--expressions)  && expressions
       - [§9.4.4.27](variables.md#94427--expressions)  || expressions
       - [§9.4.4.28](variables.md#94428--expressions)  ! expressions
@@ -328,7 +331,7 @@
     - [§12.8.3](expressions.md#1283-interpolated-string-expressions)  Interpolated string expressions
     - [§12.8.4](expressions.md#1284-simple-names)  Simple names
     - [§12.8.5](expressions.md#1285-parenthesized-expressions)  Parenthesized expressions
-    - [§12.8.6](expressions.md#1286-tuple-expressions)  Tuple expressions
+    - [§12.8.6](expressions.md#1286-tuple-literals)  Tuple literals
     - [§12.8.7](expressions.md#1287-member-access)  Member access
       - [§12.8.7.1](expressions.md#12871-general)  General
       - [§12.8.7.2](expressions.md#12872-identical-simple-names-and-type-names)  Identical simple names and type names
@@ -450,9 +453,12 @@
   - [§12.23](expressions.md#1223-assignment-operators)  Assignment operators
     - [§12.23.1](expressions.md#12231-general)  General
     - [§12.23.2](expressions.md#12232-simple-assignment)  Simple assignment
-    - [§12.23.3](expressions.md#12233-ref-assignment)  Ref assignment
-    - [§12.23.4](expressions.md#12234-compound-assignment)  Compound assignment
-    - [§12.23.5](expressions.md#12235-event-assignment)  Event assignment
+    - [§12.23.3](expressions.md#12233-deconstructing-assignment)  Deconstructing assignment
+      - [§12.23.3.1](expressions.md#122331-general)  General
+      - [§12.23.3.2](expressions.md#122332-abridged-deconstructors)  Abridged deconstructors
+    - [§12.23.4](expressions.md#12234-ref-assignment)  Ref assignment
+    - [§12.23.5](expressions.md#12235-compound-assignment)  Compound assignment
+    - [§12.23.6](expressions.md#12236-event-assignment)  Event assignment
   - [§12.24](expressions.md#1224-expression)  Expression
   - [§12.25](expressions.md#1225-constant-expressions)  Constant expressions
   - [§12.26](expressions.md#1226-boolean-expressions)  Boolean expressions

.github/workflows/markdownlint.yml

@@ -114,7 +114,7 @@ Elements of arrays created by *array_creation_expression*s are always initialize
 
 Array elements are accessed using the *array access* variant of *element_access* expressions ([§12.8.12.2](expressions.md#128122-array-access)) of the form `A[I₁, I₂, ..., Iₓ]`, where `A` is an expression of an array type and each `Iₑ` is an expression of type `int`, `uint`, `long`, `ulong`, or can be implicitly converted to one or more of these types. The result of an array access is a variable reference ([§9.5](variables.md#95-variable-references)) to the array element selected by the indices.
 
-Array elements of single-dimensional arrays can also be accessed using an array access expression where the sole index, `I₁`, is an expression of type `Index`, `Range`, or can be implicitly converted to one or both of these types. If `I₁` is of type `Index`, or has been implicitly converted to that type, then the result of the array access is a variable reference to the array element selected by the index value. If `I₁` is of type `Range`, or has been implicitly converted to that type, then the result of the element access is a new array formed from a shallow copy of the array elements with indices in the `Range`, maintaining the element order.
+Array elements of single-dimensional arrays can also be accessed using an array access expression where the sole index, `I₁`, is an expression of type `Index`, `Range`, or can be implicitly converted to one or both of these types. If `I₁` is of type `Index`, or has been implicitly converted to that type, then the result of the array access is a variable reference to the array element selected by the index value. If `I₁` is of type `Range`, or has been implicitly converted to that type, then the result of the array access is a new array formed from a shallow copy of the array elements with indices in the `Range`, maintaining the element order.
 
 The elements of an array can be enumerated using a `foreach` statement ([§13.9.5](statements.md#1395-the-foreach-statement)).
 

standard/README.md

@@ -1109,7 +1109,7 @@ It is an error if the `System.Runtime.CompilerServices.EnumeratorCancellation` a
 
 - The `EnumeratorCancellation` attribute is applied to a parameter of a type other than `CancellationToken`,
 - or if the `EnumeratorCancellation` attribute is applied to a parameter on a method that is not an asynchronous iterator ([§15.15](classes.md#1515-synchronous-and-asynchronous-iterators)),
-- or if the `EnumeratorCancellation` attribute is applied to a parameter on a method that returns an asynchronous enumerable interface ([§15.15.3](classes.md#15153-enumerable-interfaces)) rather than an asynchronous enumerator interface ([§15.15.2](classes.md#15152-enumerator-interfaces)).
+- or if the `EnumeratorCancellation` attribute is applied to a parameter on a method that returns an asynchronous enumerator interface ([§15.15.2](classes.md#15152-enumerator-interfaces)) rather than an asynchronous enumerable interface ([§15.15.3](classes.md#15153-enumerable-interfaces)).
 
 The iterator will not have access to the `CancellationToken` argument for `GetAsyncEnumerator` when no attributes have this parameter.
 

standard/arrays.md

@@ -282,7 +282,7 @@ Depending on the context in which a member declaration takes place, only certain
     > *Note*: A type declared as a member of a class can have any of the permitted kinds of declared accessibility, whereas a type declared as a member of a namespace can have only `public` or `internal` declared accessibility. *end note*
 - Struct members can have `public`, `internal`, or `private` declared accessibility and default to `private` declared accessibility because structs are implicitly sealed. Struct members introduced in a `struct` (that is, not inherited by that struct) cannot have `protected`, `protected internal`, or `private protected` declared accessibility.
     > *Note*: A type declared as a member of a struct can have `public`, `internal`, or `private` declared accessibility, whereas a type declared as a member of a namespace can have only `public` or `internal` declared accessibility. *end note*
-- Interface members implicitly have `public` declared accessibility. No access modifiers are allowed on interface member declarations.
+- Interface members implicitly have `public` declared accessibility.
 - Enumeration members implicitly have `public` declared accessibility. No access modifiers are allowed on enumeration member declarations.
 
 ### 7.5.3 Accessibility domains

standard/attributes.md

@@ -3851,7 +3851,7 @@ Once a particular non-ref-valued property or non-ref-valued indexer has been sel
 
 - If the usage is as a value ([§12.2.2](expressions.md#1222-values-of-expressions)), the get accessor shall exist and be accessible.
 - If the usage is as the target of a simple assignment ([§12.23.2](expressions.md#12232-simple-assignment)), the set accessor shall exist and be accessible.
-- If the usage is as the target of compound assignment ([§12.23.4](expressions.md#12234-compound-assignment)), or as the target of the `++` or `--` operators ([§12.8.16](expressions.md#12816-postfix-increment-and-decrement-operators), [§12.9.7](expressions.md#1297-prefix-increment-and-decrement-operators)), both the get accessors and the set accessor shall exist and be accessible.
+- If the usage is as the target of compound assignment ([§12.23.5](expressions.md#12235-compound-assignment)), or as the target of the `++` or `--` operators ([§12.8.16](expressions.md#12816-postfix-increment-and-decrement-operators), [§12.9.7](expressions.md#1297-prefix-increment-and-decrement-operators)), both the get accessors and the set accessor shall exist and be accessible.
 
 > *Example*: In the following example, the property `A.Text` is hidden by the property `B.Text`, even in contexts where only the set accessor is called. In contrast, the property `B.Count` is not accessible to class `M`, so the accessible property `A.Count` is used instead.
 >
@@ -4101,7 +4101,7 @@ An event can be used as the left operand of the `+=` and `-=` operators. These
 
 The only operations that are permitted on an event by code that is outside the type in which that event is declared, are `+=` and `-=`. Therefore, while such code can add and remove handlers for an event, it cannot directly obtain or modify the underlying list of event handlers.
 
-In an operation of the form `x += y` or `x –= y`, when `x` is an event the result of the operation has type `void` ([§12.23.5](expressions.md#12235-event-assignment)) (as opposed to having the type of `x`, with the value of `x` after the assignment, as for other the `+=` and `-=` operators defined on non-event types). This prevents external code from indirectly examining the underlying delegate of an event.
+In an operation of the form `x += y` or `x –= y`, when `x` is an event the result of the operation has type `void` ([§12.23.6](expressions.md#12236-event-assignment)) (as opposed to having the type of `x`, with the value of `x` after the assignment, as for other the `+=` and `-=` operators defined on non-event types). This prevents external code from indirectly examining the underlying delegate of an event.
 
 > *Example*: The following example shows how event handlers are attached to instances of the `Button` class:
 >