From 0642329cbe07e66def87c219410f1177afa43806 Mon Sep 17 00:00:00 2001 From: James Groom Date: Fri, 29 Mar 2024 09:58:08 +1000 Subject: [PATCH] Updated Available C# and .NET features (markdown) --- Available-C#-and-.NET-features.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/Available-C#-and-.NET-features.md b/Available-C#-and-.NET-features.md index 02f5b58..b13b64b 100644 --- a/Available-C#-and-.NET-features.md +++ b/Available-C#-and-.NET-features.md @@ -5,15 +5,15 @@ BizHawk-specific notes: - In the added "convention" column, I've used required/disallowed/encouraged/discouraged/allowed like [RFC 2119](https://datatracker.ietf.org/doc/html/rfc2119)'s MUST / MUST NOT / SHOULD / SHOULD NOT / MAY, respectively. Unsupported is also MUST NOT (because attempting to use the feature will result in an error). - Each project's target (Framework vs. Standard) is at the top of its project file, or you can check the [project graph](https://gitlab.com/TASVideos/BizHawk/-/snippets/1886666). -Legend: -✔️ Available -⭕ Available with polyfill -❌ Not available -? Unknown +Legend: +✔️ Available +⭕ Available with polyfill +❌ Not available +? Unknown Some features are marked ✔️ despite ostensibly needing a polyfill because they are enhancements to existing features and work anywhere the base feature is available—for example, `switch`ing on a `Span` requires no additional polyfill. -🔵 Availability in .NET Framework 4.8 (`net48`) -🟢 Availability in .NET Standard 2.0 (`netstandard2.0`) +🔵 Availability in .NET Framework 4.8 (`net48`) +🟢 Availability in .NET Standard 2.0 (`netstandard2.0`) I have not considered Framework 4.7.2 and below as there is little reason not to upgrade to Framework 4.8. I have not considered Framework 4.8.1 because it matches Framework 4.8 in terms of language features and is generally not useful. I use Standard 2.0 and not Standard 2.1 as the latter is not subsumed by Framework 4.8, rendering it useless.