3 ms·
Having used Copilot for a couple of hours on a Typescript/React codebase, I've encountered a very wide range of results. Sometimes, the model correctly guesses
by RandomBK 5y ago
Having used Copilot for a couple of hours on a Typescript/React codebase, I've encountered a very wide range of results.
Sometimes, the model correctly guesses exactly what I'm trying to write, and gives me non-trivial contextually correct suggestions. More than once I've been impressed enough to pause and take a screen recording of what it generated.
Other times, it's a complete mess that competes with the local language server for autocomplete corrections.
Among the misses, the most glaring issues have been when it's suggested code that violates static typing constraints. The model outputs the right contextual code, but uses variables with slightly different spelling/wording/capitalization.
This is to be expected of course, as Copilot doesn't integrate with the language server in VSCode. However it does show the limits of building the model without a native understanding of the AST it's working with.
- singularity2001 5y agomakes me wonder whether one can extend the system to filter/correct types/names
- RandomBK 5y agoI sure hope so, and given Copilot currently integrates with VSCode and its amazing language server APIs, I imagine this could be a (relatively) simple win to make a significant bump in model accuracy. I do wonder if Copilot has any idea of the structure of what it's generating though. Does it know when something is a comment, a variable, or a piece of syntax?