The inline ghost text suggestions are no longer contextually aware of existing surrounding code. If you start a new line directly above an existing function, it will "guess" at what doc comment to place there based on the next logical function one might write after the previously doc comment. Which is fine, sometimes - assuming I've demonstrated that pattern is appropriate on that codepage at that time. When I'm clearly documenting existing functions, and it clearly knows a doc comment is most likely the next action, there's no reason for it to randomly roll dice on what function might be one line below the cursor.
Forward context meaning: If I'm moving up the codepage, it's clueless about anything above the cursor. If moving down, the it's blind to what's below. Both are demonstrated in the gifs below, from two separate projects in C++ and Lua.
Notice that even when I go out of the way to nudge it in the right direction, it refuses to budge and keeps guessing at functions like the one above the cursor. This is happening all the time with actual code completions, it's not just when writing doc comments. To the point where the nonsensical suggestions not only send my train of thought careening into the ditch, but result in wasting an inexcusable amount of time trying to fight it until it's forced to consume surrounding context. And by then, of course, it's too late - damage is done, and all momentum has been lost.
Steps to Reproduce:
The inline ghost text suggestions are no longer contextually aware of existing surrounding code. If you start a new line directly above an existing function, it will "guess" at what doc comment to place there based on the next logical function one might write after the previously doc comment. Which is fine, sometimes - assuming I've demonstrated that pattern is appropriate on that codepage at that time. When I'm clearly documenting existing functions, and it clearly knows a doc comment is most likely the next action, there's no reason for it to randomly roll dice on what function might be one line below the cursor.
Forward context meaning: If I'm moving up the codepage, it's clueless about anything above the cursor. If moving down, the it's blind to what's below. Both are demonstrated in the gifs below, from two separate projects in C++ and Lua.
Notice that even when I go out of the way to nudge it in the right direction, it refuses to budge and keeps guessing at functions like the one above the cursor. This is happening all the time with actual code completions, it's not just when writing doc comments. To the point where the nonsensical suggestions not only send my train of thought careening into the ditch, but result in wasting an inexcusable amount of time trying to fight it until it's forced to consume surrounding context. And by then, of course, it's too late - damage is done, and all momentum has been lost.