2 ms·
I have no idea how well Copilot will work in practice, but, in principle, imagine a huge Cartesian space where every program in Copilot's training data is a poi
by YeGoblynQueenne 5y ago
I have no idea how well Copilot will work in practice, but, in principle, imagine a huge Cartesian space where every program in Copilot's training data is a point. Call this space S. Now suppose S contains two programs P1 and P2. Copilot should be able to represent P1, P2 and any program in S that is on a gradient between P1 and P2. If you want to write a new program, P3, such that P3 is in S between P1 and P2, then you're in luck. Otherwise you'll get garbage.
This is explained in more detail in the article below; see the first section titled "Deep Learning: the geometric view":
https://blog.keras.io/the-limitations-of-deep-learning.html https://blog.keras.io/the-limitations-of-deep-learning.html
In other words, Copilot should work well for boilerplate code and allow for many variations, but for anything more original it should be hit-and-miss. In principle. In practice, we'll know in a year or two, once enough people have used it. Or not even then.