ReSharper 2016.2 Help

Arranging Optional Parentheses

In many cases, parentheses in expressions are optional. Sometimes they help you clarify precedence of operations - e.g. if ((a & b) | c), sometimes, however, they do not help at all and just add up to dead code - e.g. var d = a + (b + c);. ReSharper will help you define where optional parentheses are helpful to you, and then either clean up the redundant parenthesis or automatically add missing ones where necessary.

ReSharper helps you arrange optional parentheses in the existing code and takes your preferences into account when it produces new code with code completion and code generation features, applies code templates and performs refactorings.

In this topic:

Enforcing preferences for optional parentheses

By default, ReSharper highlights parentheses that do not clarify operation precedence and helps remove them:

Removing redundant parentheses

Similarly, it notifies you about non-obvious operation precedences and suggests adding optional parentheses to make the code more readable:

Adding optional parentheses to clarify operation precedence

Another option to enforce your preferences for optional parentheses in a bulk mode is code cleanup. You can either run code cleanup with the default profile Default: Full Cleanup or run the cleanup with a custom profile solely targeted at your specific task as described below.

To apply preferences for optional parentheses with code cleanup

  1. Open the Code Cleanup options: ReSharper | Options | Code Editing | Code Cleanup.
  2. Create a new profile as described in the Configuring Code Cleanup section. In the Selected profile settings section for the new profile tick the Remove redundant parentheses and Add parentheses to explicitly specify operation precedence check boxes.
  3. Click Save to apply the modifications and let ReSharper choose where to save them, or save the modifications to a specific settings layer using the Save To drop-down list. For more information, see Managing and Sharing ReSharper Settings.
  4. Select the scope where you want to enforce your preferences:
    • Set the caret anywhere in the file to enforce your preferences to the file.
    • Select one or more items in the Solution Explorer to enforce your preferences in the files under these nodes and their child items.
  5. Do one of the following:
    • Press Ctrl+Alt+F or choose ReSharper | Edit | Cleanup Code in the main menu .
    • Right-click anywhere in the text editor or right-click the selection and choose Cleanup Code in the context menu.
  6. In the Code Cleanup Dialog that opens, select the newly created profile in the Available Profiles area.
  7. Click Run. ReSharper will enforce your preferences in the selected scope.

If you want to arrange optional parentheses without opening the Code Cleanup Dialog, you can bind the created profile to the silent cleanup and run it simply by pressing Ctrl+Shift+Alt+F. You can also create a custom cleanup profile that would combine applying optional parentheses style with other code style tasks.

Configuring preferences for optional parentheses

Your optional parentheses preferences are saved using the mechanism of shared settings. Among other things, this mechanism allows you to maintain different preferences for different solutions as well as to keep these preferences under a VCS and automatically share them with your team members.

To configure preferences for optional parentheses

  1. Go to the Code Editing | C# | Code Style page of ReSharper options.
  2. In the Parentheses category, specify whether to remove redundant parentheses and which operations should be considered as not having obvious precedence.
  3. The Notify with selectors in the right column allow you to set severity levels of code inspections detecting code that differs from your preferences.
  4. Click Save to apply the modifications and let ReSharper choose where to save them, or save the modifications to a specific settings layer using the Save To drop-down list. For more information, see Managing and Sharing ReSharper Settings.

See Also

Last modified: 15 December 2016