From e02523006111409b2d0e82429cb6efd330783bf7 Mon Sep 17 00:00:00 2001 From: Gauthier Segay Date: Tue, 18 Jul 2023 20:43:35 +0200 Subject: [PATCH] Update FS-1060-nullable-reference-types.md (#742) --- RFCs/FS-1060-nullable-reference-types.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RFCs/FS-1060-nullable-reference-types.md b/RFCs/FS-1060-nullable-reference-types.md index 0c4f3727..2ed6b4fd 100644 --- a/RFCs/FS-1060-nullable-reference-types.md +++ b/RFCs/FS-1060-nullable-reference-types.md @@ -984,7 +984,7 @@ All of this means that this feature is entrusting acting in good faith on the gr The primary alternative is to simply not do this. -That said, it will become quite evident that this feature is necessary if F# is to continue advancing on the .NET platform. Despite originating as a C# feature, this is fundamentally a **platform-level shift** for .NET, and in a few years, will result in .NET looking very different than it is today. +That said, it will become quite evident that this feature is necessary to continue advancing on the .NET platform. Despite originating as a C# feature, this is fundamentally a **platform-level shift** for .NET, and in last few years, .NET is looking different than it was. ### Alternative: Overall approach to nullability @@ -1007,7 +1007,7 @@ let ns1: string? = "hello" let ns2: string? = null ``` -However, this overly normalizes the use of the feature in F# and is confusing in combination with optional argumwents. +However, this overly normalizes the use of the feature in F# and is confusing in combination with optional arguments. #### Alternative: Other union-like representations