Code Inspection: Access to disposed closure
First of all, let's make sure that you understand what a closure is. To put it simply, a closure in C# is a lambda expression or an anonymous method that captures some variables from an outer scope. Here is the simplest example:
In the example above,
myStr (and not it's value) and will only get the value of
myStr when you invoke
In more complex scenarios, when a closure is defined in a changing context, it may not behave as expected.
One of the situations where it may happen is a closure defined inside a
In the above code, ReSharper issues the Access to disposed closure warning for
writer.Write(text);. The reason for that is
ExecuteDelayed() could execute the lambda after the
writer's scope is disposed, which will result in a runtime exception.
ExecuteDelayed() completes processing of the lambda on the stack, you can mark the
action parameter with the InstantHandle attribute:
This will tell ReSharper's code analysis engine that using
ExecuteDelayed() is safe in such contexts, and no warnings will be issued.