3 ms·
It's less useful than my initial impression. The reason is because Copilot does not know about the entire codebase - only the current file. This means it makes
by aurareturn 3y ago
It's less useful than my initial impression. The reason is because Copilot does not know about the entire codebase - only the current file. This means it makes a ton of mistakes.
In addition, it's often annoying because it replaces the default IDE autocomplete when you don't want it to. For example, when importing code from another file, it disables the autocomplete and then tries to make up what you're trying to import which is wrong 80% of the time as it does not know the whole code base.
There is a long running thread asking Github to disable Copilot for import statements. Thus far, Github doesn't care. Link to thread: https://github.com/orgs/community/discussions/8375 https://github.com/orgs/community/discussions/8375
- dtagames 3y agoIt is not correct to say that Copilot knows only about the current file. If I remember correctly, it tracks the last 50 opened files. In practice, especially with daily use over time, you can see it suggest code, functions, and variables from files quite "far away" in your repo. It's actually tremendously helpful when it suggests exactly what I was about to write anyway.
- aurareturn 3y agoI think it's 20/80 for me. 20% of the time, it produces working code. 80% of the time, it produces errors. Sometimes it's just more annoying to have it enabled. I'm not going to crown Copilot yet until it can read the whole code base.