Like this example: https://civet.dev/#everything-is-an-expression `items = for item of items`, in js you type `for`and copilot wrote nearly the full correct for-code. So you have to type not much and can read it easy.
Like this example: https://civet.dev/#everything-is-an-expression `items = for item of items`, in js you type `for`and copilot wrote nearly the full correct for-code. So you have to type not much and can read it easy.
(Terse Perl may be delightful to write, as long as you still remember exactly what you wrote and why. But not after that.)
``` const result = items.map( i => i.length ? i.toUpperCase() : ‘<empty>’) ```
I think things get interesting here when different kinds of iterators come into play (eg generators, async-await for loops, non-array iterables). Shame the landing page doesn’t touch on that at all.
Copilot is good when working with something where the idiomatic patterns are common, widespread, and hard to screw up. Civet has low adoption, uses much looser syntax (bracing, whitespace), and lacks the rigor of common TypeScript code.
foro
for ($1 of $2) {
$0
}
touc
toUpperCase()
le
length
map
map(x => $0)
And so on.Seriously, typing code is some '90s activity since forever. Using copilot for this is akin to hitting a nail with a microscope.