Nigel-Ecma

Clause §13.6.2 (at least) is suffering badly from features, e.g. `var` & `ref`, being introduced over time and needs a rewrite. For example it currently states that it is a...

This problem stems from proposed changes to the existing Standard introduced to cover extension methods. Unfortunately as this example shows these changes may not be rigorously and correctly defined in...

Let's consider this route through the clauses (11.8 is the old 12.7 referenced above): > 11.8 Method group conversions > ... The run-time evaluation of a method group conversion proceeds...

> On 2/07/2020, at 11:28 am, Neal Gafter wrote: > > Yes, it certainly would change the result. Here is an example: > Well that’s a fail then. (There is...

Regarding: > ## Classified as a variable > In the current V6 draft spec, we use the phrase “is [not] classified as a variable” numerous times, all in the context...

> **Proposal 1**: We should use the term “variable reference” (rather than “variable”) in all contexts involving an expression that denotes a variable. The term "variable reference" is used here,...

Would it be possible to show a v7 example of how these changes help?

`MulticastDelegate` is intentionally in neither the CLI or C# Standards. It is a historical artefact from the MS CLI implementation and is not intended to be user-visible.

@KalleOlaviNiemitalo – One could ask the same question regarding `System.Int128`, and the answer in both cases is they are unmanaged types. The issue is really the term “user-defined” which, while...

> Overall it feels like we may be missing a brief section explaining the purpose of readonly members on structs. > > I'd also expect there to be a change...