Fortsätt till huvudinnehåll

When to use out parameters in C#

The out keyword

In C# you can use the out keyword to define output parameters in your method signature. For example, the Int32.TryParse method in the System namespace has the following signature:

public static bool Int32.TryParse(string s, out int result)

From this you can read out that the TryParse method returns a boolean but also provides a result as an out parameter. The boolean will indicate whether it was possible to parse an integer value from the string s and store it in the result variable.

You can call the TryParse method like this:

if (Int32.TryParse(str, out var result))
{
    Console.WriteLine($"The result is: {result}");
}
else
{
    Console.WriteLine("Parsing failed");
}

When is it a good idea to use out parameters?

Most of the time the use of out parameters adds complexity to your program. It will make the source code harder to follow since anyone reading the code will have to juggle several return values instead of just one.

One of the most important jobs as a programmer is to minimize complexity, hence you should avoid using out parameters and as much as possible write simple methods that returns a single, obvious, result. However, there are a couple of use cases when out parameters can be useful.

The Try-Parse Pattern

I have already showed the Try-Parse Pattern in action when showing the Int32.TryParse method above. The pattern is useful in situations where the operation might fail and you want to avoid the overhead of dealing with exceptions. Throwing and catching exceptions is very bad for performance and using the Try-Parse Pattern can be a good alternative.

Returning multiple values

There might be situations where you want a method to be able to return multiple values. You could create a separate struct just for holding these values and let the method return an instance of that struct, also known as a Value object. However, if the usage is very limited, introducing a separate struct just for holding a few values might add more complexity than just introducing a few out parameters. If in doubt, create both implementations and use your best judgement on which one to keep.

Additional resources

Out parameter modifier
Exceptions and Performance (Try-Parse Pattern)
Value object

Kommentarer

Populära inlägg i den här bloggen

C# Enum as bit field

Bit field enum Whenever you wish to express combinations of properties of an object, bit fields are a good way to accomplish this. As a simple example, consider a file in the file system. It can be Readable , Writable , Hidden or a combination these. The different attributes can be defined as an enum : [Flags] public enum FileAttribute {   None      = 0b0000;   Readable  = 0b0001;   Writeable = 0b0010;   Hidden    = 0b0100; } To indicate that this enum is expected to be used as a bit field I have defined it with the FlagsAttribute . It is important to understand that the FlagsAttribute does nothing more than making some changes to how the ToString method of the enum works, making it possible to print out all flags. It does not introduce any validation or special treatment of the enum in any other way. I have defined the values of the different fields of the enum using binary representation, this should make it even more clear that this is a bit field and which bi

Codility tasks - Part I

I was recently faced with two codility tasks when applying for a job as an Embedded Software Engineer. For those of you who arn't familiar with Codility you can check out their website here:  www.codility.com Task one - Dominator The first task was called Dominator. The goal was to, given a std::vector of integers, find an integer that occurs in more than half of the positions in the vector. If no dominator was found -1 should be returned. My approach was to loop through the vector from the first to the last element, using a std::map to count the number of occurences of each integer. If the count ever reached above half the size of the vector I stopped and returned that integer and if I reached the end without finding a dominator I returned -1. So was that a good approach? Well, the reviewer at the company rated the solution as 'pretty ok'. His preferred solution was store the first integer in the array and set a counter to 1. Then loop through the remaining i