Okay, say I'm typing the following (contrived) example:
After I've typed this much:
the code completion has already selected "Empty" because that's the only
match. The line, however, looks like this because Resharper auto-closes the
Now, if I type ");" to finish the line (i.e. accept "Empty" and complete the
statement) then what I end up with is this:
Some of my coworkers are used to using the close paren to select the
intellisense suggestion and close the parens, and then just finish the
statement by typing a semi-colon, but ReSharper messes that habit up for
them because in this one specific case, it isn't taking the pre-inserted
closing paren into account. I've verified this problem on the latest build.
Any chance this will be fixed in a bug-fix release prior to 2.0?
I'll submit a tracker entry for it.