this whole thread has me like *distressed crab noises*https://twitter.com/moxie/status/1256640034054135808 …
Show this thread
-
That does assume the tools can do this. Even Rust (which has the stated benefits) has trouble often, and I've never seen, say, a code review platform with this capability for any language.
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.
- 3 more replies
New conversation -
-
-
Rust analyzer does it with... around 80% success for me. It often can't figure out the type. That will get better, of course, but I don't think it's trivial and IIUC there are some parts of it (macros) that make it unreasonably difficult -- those cases might never work well.
-
And there are cases where naming the type just isn't possible or isn't helpful. And I don't think those cases are going to go away. My point is that if it's not clear what the capabilities of a variable are from the code, that's a failure of the code that was written
- 1 more reply
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.