From 6b61be04767cb99a61cccfe42512a3fd1cbf5030 Mon Sep 17 00:00:00 2001 From: James Groom Date: Wed, 8 Feb 2023 03:44:51 +1000 Subject: [PATCH] Updated C# and .NET docs supplement (markdown) --- C#-and-.NET-docs-supplement.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/C#-and-.NET-docs-supplement.md b/C#-and-.NET-docs-supplement.md index e42bdd5..fc5cca3 100644 --- a/C#-and-.NET-docs-supplement.md +++ b/C#-and-.NET-docs-supplement.md @@ -22,7 +22,7 @@ see [feature matrix](https://github.com/TASEmulators/BizHawk/wiki/Available-C%23 There are two types of casts in C#: the C-style `(T) o` throws if the object is not of the desired type, whereas `o as T` evaluates to `null` if it's not of the desired type. There's no '?' in this `null`-producing operator (this is probably only confusing if you use Kotlin). -If an object being the wrong type is *exceptional*, throw an *exception* straight away. Having it reported as an NRE when there's no `null` in sight just delays debugging the problem. +If an object being the wrong type is *exceptional*, the method can't handle it gracefully, then throw an *exception* straight away. Having it reported as an NRE when there's no `null` in sight just delays debugging the problem. ## Type constraints (`where` clauses)