Nigel-Ecma

It’s the next day and I’m commenting on my own introductory comment on my review as an important issue probably doesn't come across clearly in the review itself: > I...

@333fred your first two comments are typos introduced during the conversion of the Standard text to Markdown, they are both correct in the previous version the Standard. Well spotted, thank...

Seems we have a resolution, produce a "more definitive" list, but that's not a quick fix but this does need resolving. Labeled to match.

Moving this to C# 7.x, when some new places expression that may be classified as nothing get introduced. Then we need to look for places where nothing is currently not...

I think we can leave the CLI references as is, I don’t think trying to find alternative wording or adding caveats is worth it. (In some sense features added to...

> I think we can leave the CLI references as is I think I'll revise that slightly, reading this issue again I see Rex quoted: > Although Microsoft’s implementation of...

@RexJaeschke Based on some testing using unconstrained type parameters with `??`: - Both arguments must be typed with the same _**unconstrained**_ type parameter, say `T` - If `T` at runtime...

I think this is now covered in #215 by the changes to writing “permitted kinds of declared accessibility” and the wording of §7.5.2 Declared accessibility

@Arthri – You need to report this issue to Roslyn, this repo is only for the C# Standard. Please create an issue with Roslyn and close this one.

@333fred – Hi Fred, @Arthi did mention the head of the thread and I did glance at it. What I did before posting was to hand convert @Arthri’s code according...