[create-pull-request] automated change (#1429)

Co-authored-by: BillWagner <[email protected]>

Author: github-actions[bot]

standard/README.md

@@ -701,11 +701,16 @@
   - [§19.3](interfaces.md#193-interface-body)  Interface body
   - [§19.4](interfaces.md#194-interface-members)  Interface members
     - [§19.4.1](interfaces.md#1941-general)  General
-    - [§19.4.2](interfaces.md#1942-interface-methods)  Interface methods
-    - [§19.4.3](interfaces.md#1943-interface-properties)  Interface properties
-    - [§19.4.4](interfaces.md#1944-interface-events)  Interface events
-    - [§19.4.5](interfaces.md#1945-interface-indexers)  Interface indexers
-    - [§19.4.6](interfaces.md#1946-interface-member-access)  Interface member access
+    - [§19.4.2](interfaces.md#1942-interface-fields)  Interface fields
+    - [§19.4.3](interfaces.md#1943-interface-methods)  Interface methods
+    - [§19.4.4](interfaces.md#1944-interface-properties)  Interface properties
+    - [§19.4.5](interfaces.md#1945-interface-events)  Interface events
+    - [§19.4.6](interfaces.md#1946-interface-indexers)  Interface indexers
+    - [§19.4.7](interfaces.md#1947-interface-operators)  Interface operators
+    - [§19.4.8](interfaces.md#1948-interface-static-constructors)  Interface static constructors
+    - [§19.4.9](interfaces.md#1949-interface-nested-types)  Interface nested types
+    - [§19.4.10](interfaces.md#19410-most-specific-implementation)  most specific implementation
+    - [§19.4.11](interfaces.md#19411-interface-member-access)  Interface member access
   - [§19.5](interfaces.md#195-qualified-interface-member-names)  Qualified interface member names
   - [§19.6](interfaces.md#196-interface-implementations)  Interface implementations
     - [§19.6.1](interfaces.md#1961-general)  General

standard/classes.md

@@ -4,7 +4,7 @@
 
 A class is a data structure that may contain data members (constants and fields), function members (methods, properties, events, indexers, operators, instance constructors, finalizers, and static constructors), and nested types. Class types support inheritance, a mechanism whereby a ***derived class*** can extend and specialize a ***base class***.
 
-Structs (§16) and interfaces (§18) have members similar to classes but with certain restrictions. This clause defines the declarations for classes and class members. The clauses for structs and interfaces define the restrictions for those types in terms of the corresponding declarations in class types.
+Structs ([§16](structs.md#16-structs)) and interfaces ([§18](ranges.md#18-extended-indexing-and-slicing)) have members similar to classes but with certain restrictions. This clause defines the declarations for classes and class members. The clauses for structs and interfaces define the restrictions for those types in terms of the corresponding declarations in class types.
 
 ## 15.2 Class declarations
 
@@ -2052,7 +2052,7 @@ A variable initializer for an instance field cannot reference the instance being
 
 ### 15.6.1 General
 
-[§15.6](classes.md#156-methods) and its subclauses cover method declarations in classes. That text is augmented by information about declaring methods in structs ([§16.4](structs.md#164-class-and-struct-differences)) and interfaces ([§19.4.2](interfaces.md#1942-interface-methods)).
+[§15.6](classes.md#156-methods) and its subclauses cover method declarations in classes. That text is augmented by information about declaring methods in structs ([§16.4](structs.md#164-class-and-struct-differences)) and interfaces ([§19.4.3](interfaces.md#1943-interface-methods)).
 
 A ***method*** is a member that implements a computation or action that can be performed by an object or class. Methods are declared using *method_declaration*s:
 
@@ -2921,7 +2921,7 @@ When an instance method declaration includes an `abstract` modifier, that method
 
 An abstract method declaration introduces a new virtual method but does not provide an implementation of that method. Instead, non-abstract derived classes are required to provide their own implementation by overriding that method. The *method_body* of an abstract method simply consists of a semicolon.
 
-Abstract method declarations are only permitted in abstract classes ([§15.2.2.2](classes.md#15222-abstract-classes)) and interfaces ([§19.4.2](interfaces.md#1942-interface-methods)).
+Abstract method declarations are only permitted in abstract classes ([§15.2.2.2](classes.md#15222-abstract-classes)) and interfaces ([§19.4.3](interfaces.md#1943-interface-methods)).
 
 > *Example*: In the following code
 >
@@ -3937,7 +3937,7 @@ An abstract property declaration specifies that the accessors of the property ar
 
 A property declaration that includes both the `abstract` and `override` modifiers specifies that the property is abstract and overrides a base property. The accessors of such a property are also abstract.
 
-Abstract property declarations are only permitted in abstract classes ([§15.2.2.2](classes.md#15222-abstract-classes)) and interfaces ([§19.4.3](interfaces.md#1943-interface-properties)). The accessors of an inherited virtual property can be overridden in a derived class by including a property declaration that specifies an `override` directive. This is known as an ***overriding property declaration***. An overriding property declaration does not declare a new property. Instead, it simply specializes the implementations of the accessors of an existing virtual property.
+Abstract property declarations are only permitted in abstract classes ([§15.2.2.2](classes.md#15222-abstract-classes)) and interfaces ([§19.4.4](interfaces.md#1944-interface-properties)). The accessors of an inherited virtual property can be overridden in a derived class by including a property declaration that specifies an `override` directive. This is known as an ***overriding property declaration***. An overriding property declaration does not declare a new property. Instead, it simply specializes the implementations of the accessors of an existing virtual property.
 
 The override declaration and the overridden base property are required to have the same declared accessibility. In other words, an override declaration shall not change the accessibility of the base property. However, if the overridden base property is protected internal and it is declared in a different assembly than the assembly containing the override declaration then the override declaration’s declared accessibility shall be protected. If the inherited property has only a single accessor (i.e., if the inherited property is read-only or write-only), the overriding property shall include only that accessor. If the inherited property includes both accessors (i.e., if the inherited property is read-write), the overriding property can include either a single accessor or both accessors. There shall be an identity conversion between the type of the overriding and the inherited property.
 
@@ -4304,7 +4304,7 @@ An abstract event declaration specifies that the accessors of the event are virt
 
 An event declaration that includes both the `abstract` and `override` modifiers specifies that the event is abstract and overrides a base event. The accessors of such an event are also abstract.
 
-Abstract event declarations are only permitted in abstract classes ([§15.2.2.2](classes.md#15222-abstract-classes)) and interfaces ([§19.4.4](interfaces.md#1944-interface-events)).
+Abstract event declarations are only permitted in abstract classes ([§15.2.2.2](classes.md#15222-abstract-classes)) and interfaces ([§19.4.5](interfaces.md#1945-interface-events)).
 
 The accessors of an inherited virtual event can be overridden in a derived class by including an event declaration that specifies an `override` modifier. This is known as an ***overriding event declaration***. An overriding event declaration does not declare a new event. Instead, it simply specializes the implementations of the accessors of an existing virtual event.
 

standard/expressions.md

@@ -381,7 +381,7 @@ A member lookup of a name `N` with `K` type arguments in a type `T` is proces
   - Otherwise, if the set contains only methods, then this group of methods is the result of the lookup.
   - Otherwise, the lookup is ambiguous, and a binding-time error occurs.
 
-For member lookups in types other than type parameters and interfaces, and member lookups in interfaces that are strictly single-inheritance (each interface in the inheritance chain has exactly zero or one direct base interface), the effect of the lookup rules is simply that derived members hide base members with the same name or signature. Such single-inheritance lookups are never ambiguous. The ambiguities that can possibly arise from member lookups in multiple-inheritance interfaces are described in [§19.4.6](interfaces.md#1946-interface-member-access).
+For member lookups in types other than type parameters and interfaces, and member lookups in interfaces that are strictly single-inheritance (each interface in the inheritance chain has exactly zero or one direct base interface), the effect of the lookup rules is simply that derived members hide base members with the same name or signature. Such single-inheritance lookups are never ambiguous. The ambiguities that can possibly arise from member lookups in multiple-inheritance interfaces are described in [§19.4.11](interfaces.md#19411-interface-member-access).
 
 > *Note*: This phase only accounts for one kind of ambiguity. If the member lookup results in a method group, further uses of method group may fail due to ambiguity, for example as described in [§12.6.4.1](expressions.md#12641-general) and [§12.6.6.2](expressions.md#12662-invocations-on-boxed-instances). *end note*
 

standard/grammar.md

@@ -2537,52 +2537,15 @@ interface_body
 
 // Source: §19.4.1 General
 interface_member_declaration
-    : interface_method_declaration
-    | interface_property_declaration
-    | interface_event_declaration
-    | interface_indexer_declaration
-    ;
-
-// Source: §19.4.2 Interface methods
-interface_method_declaration
-    : attributes? 'new'? return_type interface_method_header
-    | attributes? 'new'? ref_kind ref_return_type interface_method_header
-    ;
-
-interface_method_header
-    : identifier '(' parameter_list? ')' ';'
-    | identifier type_parameter_list '(' parameter_list? ')'
-      type_parameter_constraints_clause* ';'
-    ;
-
-// Source: §19.4.3 Interface properties
-interface_property_declaration
-    : attributes? 'new'? type identifier '{' interface_accessors '}'
-    | attributes? 'new'? ref_kind type identifier '{' ref_interface_accessor '}'
-    ;
-
-interface_accessors
-    : attributes? 'get' ';'
-    | attributes? 'set' ';'
-    | attributes? 'get' ';' attributes? 'set' ';'
-    | attributes? 'set' ';' attributes? 'get' ';'
-    ;
-
-ref_interface_accessor
-    : attributes? 'get' ';'
-    ;
-
-// Source: §19.4.4 Interface events
-interface_event_declaration
-    : attributes? 'new'? 'event' type identifier ';'
-    ;
-
-// Source: §19.4.5 Interface indexers
-interface_indexer_declaration
-    : attributes? 'new'? type 'this' '[' parameter_list ']'
-      '{' interface_accessors '}'
-    | attributes? 'new'? ref_kind type 'this' '[' parameter_list ']'
-      '{' ref_interface_accessor '}'
+    : constant_declaration
+    | field_declaration
+    | method_declaration
+    | property_declaration
+    | event_declaration
+    | indexer_declaration
+    | static_constructor_declaration
+    | operator_declaration
+    | type_declaration
     ;
 
 // Source: §20.2 Enum declarations