Intellisense issues with commit on space and other punctuation

[danquirk]

VS now commits completion lists on more than tab and enter, including space and a variety of punctuation characters (semicolon, parens, brackets, etc). There are places where we offer completion lists that we shouldn't, or poor completion lists, which were previously visual distractions but now are significant annoyances in the actual typing experience, requiring constantly dismissing completion lists via Esc to type what you intended.

Fat arrow functions

Typing a space after the fat arrow argument commits a suggestion that is never correct, and then happens frequently in the body as well.

Type argument declarations

Tracked here #1428

Destrucuring Assignments

Not supported in the editor yet but will need to work like var declaration completion lists.

There are likely other cases as well but these ones stand out immediately. This also ties into #315 which is asking for a toggle on this behavior. Depending on the fix we use for this behavior we may also have some significant test costs associated with these fixes.

[Peter-Juhasz]

Sometimes an Esc is better than an Enter every single time. :) You are on the right track.