{"id":371615,"date":"2023-07-14T14:52:41","date_gmt":"2023-07-14T13:52:41","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=dotnet&p=371615"},"modified":"2025-09-17T14:21:38","modified_gmt":"2025-09-17T13:21:38","slug":"rsrp-rider-2023-2-eap9","status":"publish","type":"dotnet","link":"https:\/\/blog.jetbrains.com\/en\/dotnet\/2023\/07\/14\/rsrp-rider-2023-2-eap9","title":{"rendered":"Extended C# Support in ReSharper and Rider 2023.2 EAP 9"},"content":{"rendered":"\n

We\u2019ve just published new EAP builds for both ReSharper 2023.2<\/a> and Rider 2023.2<\/a>. Both contain updates to C# support. Let\u2019s dive in! <\/p>\n\n\n\n

C#12 preview support <\/h2>\n\n\n\n

Primary constructors <\/h4>\n\n\n\n

In the 2023.2 version, we introduced primary constructor support for non-record<\/code> classes<\/code> and structs<\/code> from the C# 12 preview. Unlike primary constructors in records<\/code>, primary constructors in classes<\/code> and structs<\/code> do not implicitly declare members such as properties or fields. Instead, you can use the primary constructor parameters all over the type declaration. The compiler will figure out how to make the parameter value available in the context of usage. This may greatly reduce the amount of code repetitions.<\/p>\n\n\n\n\"\"\n\n\n\n

While the ability to make use of primary parameters in all instance members of type declarations is powerful, some of you may find this implicit “capture” of primary parameters into a type’s state a bit confusing. To make things more intuitive, we introduced additional coloring for “captured” primary constructor parameters. The default color is now the same as the ordinary fields\u2019 colors. As a result, it helps you easily differentiate ordinary method parameters from primary constructor parameters in the parameter list of the type.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

The ReSharper and Rider 2023.2 EAP builds can now detect those types where the initialization can be expressed with new primary constructors. It can also suggest if private fields may be completely replaced by the use of primary constructor parameters. C# 12 now also supports the ability to add attributes for primary constructors (in class<\/code>, record<\/code>,<\/em> and struct<\/code>) by using the method<\/em>:<\/code> attribute target. The corresponding quick-fix to use the primary constructor will handle everything for you.<\/p>\n\n\n\n\"\"\n\n\n\n

Sometimes, the initialization of the type must be made less trivial and can no longer be expressed using a primary constructor. For such cases, we introduced context actions to convert the C# 12 primary constructors back to ordinary ones. <\/p>\n\n\n\n\"\"\n\n\n\n

As usual, you can also do a reverse replacement from primary constructor parameters to ordinary fields if you need to make a captured state available for derived classes with protected fields or if you need to annotate a field with an attribute.<\/p>\n\n\n\n\"\"\n\n\n\n

Other updates<\/h4>\n\n\n\n

Besides the primary constructors for non-record<\/code> classes<\/code> and structs<\/code>, we added support for one more feature from the C# 12 preview. <\/p>\n\n\n\n

You can now use ;<\/code> instead of the empty <\/em>{ }<\/code> block for type declarations for class<\/code>, struct<\/code>, interface<\/code>,<\/em> and even enum<\/code> declarations. The ReSharper and Rider 2023.2 EAP builds suggest you use this new syntax. You can then apply the quick-fix for different scopes including file, folder, project, and the entire solution.<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Support for the IAsyncDisposable<\/code> interface <\/h2>\n\n\n\n

In addition to a few inspections to catch an early disposal of using<\/code> variables, which we introduced in the EAP 5 build<\/a>, we improved the Generate dispose pattern<\/em> feature to support the IAsyncDisposable<\/code> interface and be able to generate an async method to release the resources.<\/p>\n\n\n\n\"\"\n\n\n\n

Better C# discards support <\/h2>\n\n\n\n

Both ReSharper and Rider 2023.2 EAPs received a bunch of new useful additions to C# discard support. As you may know, discards are placeholder variables that are intentionally unused in application code.<\/p>\n\n\n\n

You can now quickly check names and types of discarded values with Push-to-Hint<\/em> functionality. Press and hold the Ctrl<\/kbd> <\/em>key to activate the Push-to-hint<\/em> mode. <\/p>\n\n\n\n\"\"\n\n\n\n

Since _<\/code> is a valid name of an identifier in C#, we introduced some inspections to reduce the possibility of confusing _<\/code> as a discard symbol. It can prepare your code for upcoming breaking changes<\/a> in C#.<\/p>\n\n\n\n

There is now a warning about variables and parameters named _<\/code> that are actually being used. They look like a “discarded” value, but in reality, they represent very much the opposite. To clarify the code, we now offer the quick-fix to rename the lambda parameter.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Also, we detect older code patterns that existed before the discard assignment was introduced in C# and offer the quick-fix \u2013 Use discard assignment \u2013<\/em> to rewrite the code in a more idiomatic way using discards.<\/p>\n\n\n\n\"\"\n\n\n\n

That\u2019s it for today! <\/p>\n\n\n\n

The full list of improvements and fixes can be found on YouTrack:<\/p>\n\n\n\n