JetBrains Rider 2021.3 Help

Type-matching completion

This command filters the list of types, methods, and variables to match the expected type of an expression. It works anywhere as long as JetBrains Rider can determine the expected type of the expression, for example, right-hand sides of assignments, variable initializers, or return statements. If several return types are possible, JetBrains Rider detects the most recently used symbol of an applicable type and automatically selects it in the lookup list. Type-Matching Completion can also suggest creating anonymous delegates, lambda expressions, and regular methods, as well as local variables for out parameters. In addition to that, in object initializers, Type-Matching Completion suggests fields/properties that were not yet assigned a value.

Invoke type-matching completion

  1. Place the caret at the position where you're going to type your code.

  2. Press Ctrl+Shift+Space.

  3. Select a suggestion from the list and press Enter or start typing the initial letters of the identifier or its CamelHumps abbreviation to narrow down the list of suggestions.

When you use code completion over existing code items, you can either insert the selected completion suggestion before the existing item by pressing Enter or replace the existing identifier with the selected suggestion by pressing Tab. If necessary, you can change the default shortcuts on the Keymap page of JetBrains Rider settings Ctrl+Alt+S (look for the Choose Lookup Item and Choose Lookup Item Replace actions) .

When you select items in completion lists using keyboard, the selection will jump to the first item after the last item and vice versa. You can disable this behavior by clearing Cyclic scrolling in list on the Appearance and Behavior | Appearance page of JetBrains Rider settings Ctrl+Alt+S.

Exclude types and namespaces from completion suggestions

You may want some types or namespaces not to be suggested, for example, if you have something similar to a system type in your solution, say MyFramework.MyCollections.List, but you are not actually using it. To exclude such items from the suggestions, add them to the Exclude from import and completion list on the Editor | General | Auto Import page of JetBrains Rider settings Ctrl+Alt+S.

The format of the entries is Fully.Qualified.Name, Fully.Qualified.Name.Prefix*, or *Fully.Qualified.Name.Suffix. Generic types are specified as List`1.

Examples of type-matching completion

You can use the following examples to get an idea of how smart type-matching completion works with various code items:

After a return statement

JetBrains Rider: type-matching completion after return statement

In the right-hand side of assignments

JetBrains Rider: type-matching completion in the right-hand side of assignments

In cast expressions

Before:

JetBrains Rider: type-matching completion in cast expressions
After launching Type-Matching Completion (since there's a single option in this case, JetBrains Rider inserts the expected type without displaying a list):
JetBrains Rider: type-matching completion in cast expressions

In object initializers

JetBrains Rider provides Type-Matching Completion for setting properties in object initializers that were not previously set for a particular object:

JetBrains Rider: type-matching completion in object initializers

In lambda expressions

In addition to traditional anonymous and named methods, Type-Matching Completion readily generates lambda-expression syntax:

JetBrains Rider: type-matching completion in lambda expressions

Creating a local variable in place of an out parameter

JetBrains Rider: type-matching completion. Creating a local variable in place of an out parameter

Using CamelHumps

JetBrains Rider: type-matching completion. Using CamelHumps
Last modified: 07 April 2022