this whole thread has me like *distressed crab noises*https://twitter.com/moxie/status/1256640034054135808 …
Show this thread
-
The capabilities of something are typically much more important than the concrete type. Hell often the type is either unnameable or unreasonably difficult to name. Features like async/await are making this even more common.
For code review -- why is the variable declaration site the place that we should force a type to be explicitly declared? It's just as likely for me to review a PR that adds `http://foo.do _thingy()`, why not force UFCS here for clarity?
-
-
My point wasn't so much that variables need to be declared at the point of use (I did say I didn't really agree with moxie here), but more that relying on tooling to solve these problems ignores the large class of situations where such tooling does not and likely never will exist
-
I definitely agree with you that we shouldn't rely too hard on tooling here. But ultimately tooling is a shortcut for looking up the definition of the method definition -- tools like ctags aren't exactly new. Macros will always make this be unsolvable in the general case
End of conversation
New conversation -
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.