This can lead to unexpected behavior and resource-related issues. Returning an object captured by a using statement can be problematic because it extends the lifespan of the returned object beyond the method scope, causing the object to be disposed of immediately after returning. When a variable is captured by a using statement, it ensures that the object is properly disposed of when it goes out of scope. Rider 2023.2 introduces two new code inspections designed to address scenarios where the state of a returned object may be negatively influenced by its early disposal or the early disposal of the object that spawned it. New inspections for improved control over object disposal

This inspection will also be triggered when an invocation has an argument value that is the same as the default value of the parameter in the invoked delegate, making the expression redundant.

In addition to the standard set of warning messages associated with recognizing this syntax, we’ve also tweaked an existing inspection, The parameter has the same default value, to account for default parameter values in lambdas. C# support Support for default parameter values in lambdasĪs part of our work on supporting C# 12 language updates, we’re introducing support for default parameter values in lambda expressions in Rider 2023.2. But before you download this build, let’s go over the most important updates it contains. The latest installment in our Early Access Program for Rider 2023.2 is here.

Instaling JetBrains Rider 2023.1.3