What’s new in ReSharper 2022.2

In C# 11, class, struct, and record types gained the ability to declare a list of required members. This is the list of all properties and fields that are considered required and must be initialized during the initialization of a type’s instance. Types inherit these lists from their base types automatically, providing a seamless experience that removes boilerplate, repetitive code.

Apart from being aware of the required keyword for members inside a class, struct, or record type, ReSharper provides additional support for the required keyword:

• There is a required keyword in the code completion.
• Most of the compiler errors and warnings are available.
• The required modifier has been added to the Modifiers order on the ReSharper | Options | Code Editing | C# | Syntax Style page.

We’ve added a new Add initializer for required members quick-fix for cases where you’ve created a type’s object but haven’t initialized the members yet. It automatically generates all of the missing “required” members for your object – you just need to fill in the members’ values with meaningful data.

In this release, we've greatly optimized the memory usage of ReSharper with the Solution-Wide Analysis mode turned ON, both in terms of memory traffic (number of memory allocations) and in terms of memory consumption.

The Solution-Wide Analysis engine uses memory to store the list of issues in the solution and to store the type/member usage information to perform solution-wide usage reporting (code inspections like "public member is never used"). The usage data is "hot", meaning it needs to be constantly updated while you are editing the code, and can’t be off-loaded to the disk. This can consume a significant amount of memory if your solution contains lots of types and type members. We reviewed the data stored in memory and found patterns that allowed us to deduplicate/normalize the data. We also utilized specialized collection types to further reduce the working set. These optimizations resulted in a 5-10x memory consumption improvement and faster Solution-Wide Analysis loading.

We’ve introduced the Virtual Formatter — a way for you to view code with your desired formatting without actually reformatting the source code on the disk. For example, you can now virtually align parameters in columns or increase indents. Our goal with this feature is to improve readability and maintainability of code and make it more accessible for visually impaired and neurodivergent developers. To enable the Virtual Formatter with predefined settings, go to ReSharper | Options | Environment | Inlay Hints | General. To further tailor the formatting to your exact specifications, check the Use dedicated Virtual Formatter style settings checkbox and click C#.

You can now remove temporary files generated by ReSharper while it is working on your code. We’ve added a new page in Options where you can:

• Observe a set of default paths and files ReSharper can remove.
• Add a custom path template for files you want to be removed.
• Specify after how many days ReSharper should consider files outdated for each path template.
• Check how much space is occupied by files matched by each path template.
• Set up automatic cleanup for outdated files which will run periodically (the default value is 1 day).
• Run the cleanup manually for different scopes.

As many of you might have noticed, JavaScript and TypeScript support in ReSharper is outdated and slow. In the current implementation, it's difficult to follow TS language changes and support new versions quickly, so we are looking for a better way to support these languages. After a long internal discussion, we've decided to put our current JS and TS support on hold. As a result, we've disabled TS/JS support by default in this release. If you still want to use it, you can re-enable it here: ReSharper | Options | Environment | Products & Features | the "JavaScript and TypeScript" checkbox.

ReSharper C++ introduces Blueprint-specific inlay hints and allows you to see the bigger picture behind your code:

• Be aware of derived Blueprint classes and check out the list of all inheritors.
• Spot that a UFunction has implementations in Blueprints and search for all such cases.
• Quickly check the state of a UProperty, including whether it has been overridden and what value is set in the Blueprint file.

We’ve also added inspections to let you know if there are inconsistencies between the Blueprint-specific function specifiers used in the code and the Blueprints themselves.

dotTrace now provides more details for native system calls in the Timeline Call Tree, including Windows kernel calls (ntoskrnl.exe), device driver calls (*.sys), and more.