Skip to content
"Must use return value" Roslyn code analyzer and code-fix provider for C# implemented in F#
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Emit a compilation error if a method's return value is not used.

(This analyzer is based on ReturnValueUsageAnalyzer by Richard Gibson).


The motivation is to help mitigate the finishing problem of fluent interfaces.

[...] a particular challenge of fluent interfaces and method chaining known as the “finishing problem.” To illustrate it, consider a logging framework. It might allow some number of chained methods such as Severity(), Source(), User(), CallSite(), etc.:

Log.Message("Oh, noes!").Severity(Severity.Bad).User("jsmith");

Looks nice, right? The problem here is that the logging framework doesn’t know when to write the log message to the log file.
Do I do it in the User() method?
What if I don’t use the User() method or I put it before the Severity() method, then when do I write to the file?
This problem occurs any time you want the entire result of a method chain to take some external action other than manipulating the context of the chain.

Specifically, the analyzer makes it possible to enforce calling of the terminating method.

Terminating Method

This first technique is probably one of the easier [...]
It requires the introduction of a method that serves to complete the chain and act on it’s final context. For example:

Log.Message("Oh, noes!").Severity(Severity.Bad).User("jsmith").Write();

See how we added the Write() method there at the end?
That Write() method takes the chain context, writes it to disk, and doesn’t return anything (effectively stopping the chain).

So why is this so bad? For one, it would be very easy to forget the Write() method at the end of the chain. This technique requires the programmer to remember something that the compiler can’t check and that wouldn’t be picked up at runtime if they forgot.

Well, the MustUseRetVal analyzer can emit a compile-time error if the terminating method call is missing.
And so this approach isn't that bad anymore!

To get back to the loggin example, let's say the Log class looks something like this:

public class Log {
    // ...
    public static Log Message(string message) { return new Log(message); }
    public Log Severity(SeverityKind severity) { /* ... */ return this; }
    public Log User(string userName) { /* ... */ return this; }
    public void Write() { /* ... */ }

OK, so, the programmer forgot to end a chain with a call to the Write method:

Log.Message("Oh, noes!").Severity(Severity.Bad).User("jsmith");

As the User method is marked with [MustUseReturnValue], the code above will cause the analyzer to emit a compile-time error along these lines:

The return value of `User` must be used.

Download and install

Install the MustUseRetVal nuget package. For example, run the following command in the NuGet Package Manager Console.

Install-Package MustUseRetVal

This will download all the binaries, and add necessary analyzer references to your project.

How to use it?

  1. Introduce MustUseReturnValueAttribute attribute to your solution.
    I. e., create your own
    class MustUseReturnValueAttribute : Attribute { }
    Or use an existing one.
    For example, from ReSharper's JetBrains.Annotations.
    If you decide to go with JetBrains.Annotations, make sure to define the JETBRAINS_ANNOTATIONS symbol — so that the MustUseReturnValue attribute is compiled into the resulting assembly.
  2. Pick a method the return value of which must not be ignored by the calling code. Annotate the method with the [MustUseReturnValue] attribute.
  3. Install the nuget package into the project(s) which contain code calling the annotated method(s).

How does it work?

  1. This analyzer looks at expression statements.
  2. If an expression statement's underlying expression is an invocation expression (e.g., a method call), the analyzer then finds the method's definition.
  3. If the definition is annotated with a [MustUseReturnValue] attribute (the comparison is performed by name),
    the analyzer requires the method's return value not to be discarded implicitely.

The MustUseRetVal analyzer in action

Technical details

The analyzer, code-fix provider, and tests are implemented in F#

Thank you!


The MustUseRetVal analyzer and code-fix provider are licensed under the MIT license.
So they can be used freely in commercial applications.

You can’t perform that action at this time.