Bug in code completion with closing parens

Okay, say I'm typing the following (contrived) example:

string.Compare("", string.Empty);

After I've typed this much:

string.Compare("", string.Em

the code completion has already selected "Empty" because that's the only
match. The line, however, looks like this because Resharper auto-closes the
parens:

string.Compare("", string.Em)

Now, if I type ");" to finish the line (i.e. accept "Empty" and complete the
statement) then what I end up with is this:

string.Compare("", string.Empty);)

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.

- Paul


1 comment
Comment actions Permalink

Hello Paul,

This is a known problem and is already fixed in 2.0. Thanks for reporting
it.

Oleg Stepanov
Software Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Okay, say I'm typing the following (contrived) example:

string.Compare("", string.Empty);

After I've typed this much:

string.Compare("", string.Em

the code completion has already selected "Empty" because that's the
only match. The line, however, looks like this because Resharper
auto-closes the parens:

string.Compare("", string.Em)

Now, if I type ");" to finish the line (i.e. accept "Empty" and
complete the statement) then what I end up with is this:

string.Compare("", string.Empty);)

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.

- Paul



0

Please sign in to leave a comment.