Skip to content
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

Publish updated nullable reference type spec #21344

Merged
merged 1 commit into from Nov 5, 2020

Conversation

BillWagner
Copy link
Member

See dotnet/csharplang#4100

Move the included specification for nullable reference types to the C# 9 folder.

Update the appropriate title metadata.

Because nullable reference types was a C# 8.0 feature, I am publishing this speclet in both C# 8.0 and C# 9.0.

See dotnet/csharplang#4100

Move the included specification for nullable reference types to the C# 9 folder.

Update the appropriate metadata to match.
@@ -88,6 +88,8 @@
href: ../../../../_csharplang/proposals/csharp-9.0/records.md
- name: Top-level statements
href: ../../../../_csharplang/proposals/csharp-9.0/top-level-statements.md
- name: Nullable reference types - specification
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does this appear twice?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because the feature was added in C# 8.0, and is now being updated for C# 9.0. I think it will help findability. On the other hand, do you think it will be confusing to appear twice?

Copy link
Contributor

@gewarren gewarren Nov 5, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's probably fine. I did notice in the preview that "proposal" should be plural in the top level node for 8 and 9. (Lines 61 and 85.)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@BillWagner Not sure if you saw the previous comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants