this whole thread has me like *distressed crab noises*https://twitter.com/moxie/status/1256640034054135808 …
Show this thread
-
rust-analyzer definitely does do this (which is admittedly a young technology). But this whole argument also assumes that the type of a variable is always (or even often) a useful thing to see, which I don't believe is the case.
If we assume it *is* for a second, the tradeoff here is "I need tooling to expose the type at the point where a variable is assigned" vs "I need tooling to help me change every call site if I change the return type of this function".
-
-
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?
- 2 more replies
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.