C-Sharp | Java | Python | Swift | GO | WPF | Ruby | Scala | F# | JavaScript | SQL | PHP | Angular | HTML
We develop a reliable array property that avoids errors in foreach-loops. MSDN suggests a specific design pattern that does not use the null value, even when there is no data.
Example. Here we see an interesting way to simplify your code that returns string arrays. If you have a method or property that returns null and you use that result in a foreach-loop, your program will throw a NullReferenceException.
However: You can instead return an empty string[0] array. This array could be cached in some programs.
C# program that demonstrates array property class Program { static void Main() { foreach (string item in Empty) { System.Console.WriteLine(item); // Never reached } } /// <summary> /// Get an empty array. /// </summary> public static string[] Empty { get { return new string[0]; // Won't crash in foreach } } } Output No output.
The code shows that when you loop over an empty string array, you will never execute the loop contents. If you instead had Empty return null, you would hit the NullReferenceException. This could make your code more complex.
The Empty property above might do some kind of processing before it decides to return the empty array of zero length. You might have code that checks a backing field each time, and if the field is null, returns the empty array.
Discussion. Let's look at MSDN and see the usage guidelines for the .NET Framework. In the document Array Usage Guidelines, it is suggested that null array references not be returned, even when the backing store is null.
String and Array properties should never return a null reference. Null can be difficult to understand in this context.
Summary. We looked at how you can return an empty array from a public property in a C# program. When users of this property try to use the foreach-loop on the empty array, no exception will be thrown. The code in the foreach-loop will not execute.
And: This results in more reliable and simpler software, with the only downside being a null check in the property.