-
Notifications
You must be signed in to change notification settings - Fork 92
Post #681 review and grammar testing update #1473
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: draft-v8
Are you sure you want to change the base?
Conversation
- dotnet#681 has been merged before completion to reduce the conversation & change complexity. This is a review of this PR changes now in draft-v8. Every change will be augmented by a comment in the new PR - Grammar testing, updates post dotnet#681 - Update tarball to v2.3.7 - Add sample “Expanded Interfaces”
|
Closing & reopening to refresh tools |
|
Reopening with refreshed tools… |
BillWagner
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is good. I upvoted all the standard changes I agreed with, and added comments on the few others I had feedback on.
| ### 19.6.5 Interface mapping | ||
| A class or struct shall provide implementations of all abstract members of the interfaces that are listed in the base class list of the class or struct. The process of locating implementations of interface members in an implementing class or struct is known as ***interface mapping***. | ||
| A class or struct shall provide implementations for all abstract members of the interfaces that are listed in the base class list of the class or struct which do not have a reachable implementation; where an implementation can become unreachable due to reabstraction [§19.4.3](interfaces.md#1943-interface-methods). The process of locating implementations of interface members in an implementing class or struct is known as ***interface mapping***. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As @BillWagner observed my first attempt to improve this didn’t cover reabstraction. Wordsmithing this in was a challenge, the reabstraction could be said to “hide” the existing implementation – but I don’t think we want to use word here. I settled on “(un)reachable” but maybe someone can do better? (@RexJaeschke?)
Same change made to line 1466 below
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like it.
|
Close & reopen to refresh tools |
|
Reopen… |
Review: #681 has been merged before completion to reduce the conversation & change complexity. This is a review of this PR’s changes now in draft-v8. Every change will be augmented by a comment in this new PR
Grammar testing: Add sample “Expanded Interfaces” to cover #681 changes. Update tarball to v2.3.7
Review notes:
The changes to files in /standard should be read as “review suggestions” – as in the changes may, or may not, be accepted. Each one is commented.
Of all the other files the only one you may wish to read is /tools/GrammarTesting/Tests/Parsing/Samples/v8/Expanded Interfaces/sample.cs. This is the trivial sample added to check that all the new members of interfaces are parsed as expected.