I've now used Copilot for about an hour for some Typescript / React code. It's remarkably good for the reasons in QT. The integration is seamless, and the suggestions are good enough that I would absolutely continue using it.https://twitter.com/Skiminok/status/1409961752620539904 …
-
Show this thread
-
Example 1: adding a "footnotes" feature. Left, Copilot correctly infers (a) I want a <sup> tag and (b) I want the # of sections as the content. Right, after writing class="footnotes", Copilot correctly infers the data structure and 95% of the .map function I was about to write.pic.twitter.com/g0ef7XlWxl
1 reply 0 retweets 1 likeShow this thread -
Example 2: adding a key to a dictionary if it doesn't already exist. I just have to write the start of the predicate, and Copilot correctly infers the rest. (These are all the first suggestion btw, no cycling.)pic.twitter.com/uA4KS4ItxS
1 reply 0 retweets 2 likesShow this thread -
Example 3: I have a code pattern of creating a React context using the <X>Context = X<Data> template. Copilot picks up on this and infers that I want a SectionContext for my SectionData.pic.twitter.com/44txyJqHbZ
1 reply 0 retweets 1 likeShow this thread
Most of the focus, esp criticism, has been about the doc string -> function body. But in terms of day-to-day development, that stuff is way less important than the small contextual autocompletes like the ones above.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
cognitive psychology. PhD