Visual Studio insists on autocorrecting the method name I type to a similarly named field

[vsfeedback]

This issue has been moved from a ticket on Developer Community.

---

I am coding a C# class that has a switchedTime field above the keyboard cursor and a SwitchTime() method below. Admittedly, my code includes an unclosed brace, which could be preventing Roslyn or whatever is used in the back to recognize that the SwitchTime() method exists, but it should at least be able to scan the rest of the code for matching words, yet as soon as I type this.Sw - it auto-"corrects" it to this.sw and suggests completing it to this.switchedTime. I hit backspace twice to let revert the autocorrect and type what I intended and it auto-"corrects" me again. The only way I can type what I intended is by typing "S" and then "(", which very unhelpfully replaces the "S" with "SetTitleBar" and then backspacing through it all to type it again since once I have the opening parenthesis following the name it doesn't recognize - it seems to stop fighting me. VS should at least follow the long tradition of Office, where temporarily disabling autocorrect is as simple as pressing backspace.

I have a feeling that recently VS philosophy is that we only write code top to bottom and never edit it afterwards. I think somewhat recently it started insisting that every time I type a double quote - it needs to add another one to the right of the cursor (seemingly following the VS Code default), while in many if not most cases I actually want to type a double quote just before some string of already type text, so every time I do that - I end up with a string that starts and ends with two double quotes until I go back and fix those. I tried turning that off, but the only option to do so seems to be "Automatic brace completion", which also disables any other automatic quote/parenthesis/bracket/brace completion, likely increasing the chance of this new autocorrect being unable to recognize half of the symbols in my .cs file.

The unhelpful autocorrect functionality:

The code underneath the popup, which gets ignored and rejected:

---

Original Comments

Feedback Bot on 7/21/2024, 08:30 PM:

(private comment, text removed)

---

Original Solutions

(no solutions)

[sharwell]

The recovery here is poor. One of two things should have happened:

1. The missing brace implicitly inserted before private, and recovery allows IntelliSense to be aware of the SwitchTime method.
2. The missing brace is not implicitly inserted before private, and recovery allows IntelliSense to be aware of SwitchTime as a local function.

I'm guessing the latter did actually happen, but SwitchTime was filtered out of completion due to typing this..

[CyrusNajmabadi]

Accessibility modifiers should ensure that we do '1'. If not, that's a parser bug.

[CyrusNajmabadi]

I have a feeling that recently VS philosophy is that we only write code top to bottom and never edit it afterwards

This is not the case. This is just an example of poor error recovery due to the language getting more constructs that are ambiguous.