* Updated status of null coalescing assignment from proposed to implementation completed
The feature is available in C# 8. I can't see guidance on what should be updated in these docs to reflect that, so not sure if what I've changed is what should be changed!
* Update null-coalescing-assignment.md
Marking all stages of null coalescing assignment proposal as completed with checkbox filling
* Added details and examples for null guard guidance
* Update proposals/csharp-8.0/nullable-reference-types.md
Co-Authored-By: Bill Wagner <wiwagn@microsoft.com>
Co-authored-by: Bill Wagner <wiwagn@microsoft.com>
Fixesdotnet/docs#13841
I added a note (first recommendation) but did not make any additions for the second. That's covered in more of the tutorials and conceptual docs.
* fold ranges changes into initial spec
See https://github.com/dotnet/docs/issues/12772#issuecomment-501451870
This will read better as a coherent story for the Range and Index features as delivered.
* update the description of Slice.
* update precedence rules for range expression.
* Simplify language to move from a proposed design to a spec
This removes some of the history and concerns with the previous design.
* markdown lint fixes for 8.0 proposals
Summary:
1. a few header formatting fixes
1. use `csharp` or `antlr` as the language identifier for code fences.
1. update links to relative links for articles published on docs.
* change the links to records.md to absolute links
When published on docs.microsoft.com, the links from these proposals will resolve to the source on dotnet/csharplang.
That's the desired behavior for records.md, because that is a proposal feature that has not been implemented.
