You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* updates for using static
Current spec text for using static
proofread fixes
* add example for inheritance and static using
I chose to use non-descript names rather than provide an example from the class library. I think that's sufficient to understand, and doesn't beg more questions about the design decision (even in an informative example).
* fix duplicate header
* fix CI build
* fix build warning
* Apply suggestions from code review
Co-authored-by: Jon Skeet <[email protected]>
* respond to feedback
* braces on end of line
I wanted to check other clauses in the standard to compare. Jon is correct.
* respond to public feedback.
* Format samples
Make the following changes to the code samples in this clause:
- Add a blank line between peer elements *except* for multiple `using` directives and multiple `alias` directives. (I did add a blank line between `using` and `alias` directives.
- Use Allman brace style on non-empty `class` declarations. (I'd prefer using Allman brace style on methods, but the standard currently uses K&R style for methods consistently.
Co-authored-by: Jon Skeet <[email protected]>
0 commit comments