That seems a lot more complicated than from '<autocomplete joy>' import <autocomplte joy>;
-
-
Replying to @jaffathecake
for the IDE to implement or for the user to use?
1 reply 0 retweets 1 like -
-
Replying to @jaffathecake
I think that's true, but marginal. "Snippets" that jump the cursor around have been an editor fixture for years.
2 replies 0 retweets 0 likes -
Replying to @wycats @jaffathecake
Also, I've heard there's a maxim about optimizing for readers not writers...
#TheZenOf1 reply 0 retweets 2 likes -
Replying to @wycats @jaffathecake
Snark aside, "import is a keyword" is a high order bit here.
2 replies 0 retweets 0 likes -
-
import 'stuff' as { moduleName as otherThing }
2 replies 0 retweets 1 like -
Replying to @jaffathecake @kpk
The two `as`es there are confusing to me personally.
2 replies 0 retweets 2 likes -
See my other tweets about leapfrogging improvements that involve managing the list of imports for you from the usage site.
1 reply 0 retweets 0 likes
VSCode/TS try to do this, and when it works, it's magical.
-
-
As long as it doesn't involve a factory, I'm good with whatever :)
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.