Resharper's Intellisense slow down coding

Hello, guys!
I'm using Re#er 4.1 (and this issue was with previous versions). Problem: on clear VS when I type 're', studio immediately shows popup with 'return' word. After Re#er it just stupidly underline 're' with red "Unexpected token". Sometimes it works as expected - showing popup with suggested words, but again with problem: my 'return' stay at bottom, but damn 'ReferenceEquals' on first place! (never used it).
So... my suggestion: please, pay attention to intellisense and COUNT usage statistic on words (sorting words accordingly).
And fix bug when popup doesn't appear.

1 comment

"please, pay attention to intellisense and COUNT usage statistic on words (sorting words accordingly)."

Please don't. One of the biggest problems that R# has right now is that its default selections are almost never what you want. You are quite right about that.

However, sorting by and defaulting on anything other than shortest match (which is something R# fails to do in many places right now) causes me to have to take my right hand off the home row, move to the cursor keys, slew through the list to get to the right choice (remember, if R# sorts on anything other than shortest match -> longest match, if I want the short match and it doesn't pick it at first I can't type any more characters to get to it, as the word has no more characters in it), then re-home my right hand. Moving back and forth to the cursor keys is WAY slower than typing more characters when you want a longer match.

You might think that this will cause more typing when the match you tend to use more is longer, but I'd put money on my recommendation saving net keystrokes and time (especially due to avoiding the cursor key jump and jump back) especially when combined with R#'s very (thankfully!) capable camel-case based filtering (which means that almost any longer choice is very, very few keystrokes away)

As a more general aside: JetBrains should consider monitoring the amount of cursor key usage while using R# features. Any time a cursor key gets pressed, the developer responsible for the feature that caused the user to have to use the cursor key should receive a mild electric shock. :) Similar monitoring could also be put in place for the times when a user has to stop typing and use a hand to move the mouse while using a R# feature. A slightly larger shock should occur in this case because the mouse is even farther away from the home row.


Please sign in to leave a comment.