3 ms·
Vim vs emacs, auto inference vs explicit, I don't think it will ever end. :)
by arunc 6y ago
Vim vs emacs, auto inference vs explicit, I don't think it will ever end. :)
- jbverschoor 6y agoAren't there any type synthesizers which modify your code based on inferenced types?
- thesuperbigfrog 6y agoIsn't that called weak typing? (https://en.wikipedia.org/wiki/Strong_and_weak_typing#Definitions_of_%22strong%22_or_%22weak%22 https://en.wikipedia.org/wiki/Strong_and_weak_typing#Definit...)
- jbverschoor 6y agoNo. I mean altering code to strong typing using type inference. So that auto becomes int, or MyClass*.
- lostmsu 6y agoIt already ended. VSCode and auto inference.
- takeda 6y agoI don't know D, but after reading more comments looks like auto is also compensating for poor type system. For example functions that accept arguments of many types apparently need to be declared that are returning auto. At least that's what I understood.
- jane_red 6y agoScala has a strong type system and when working with it on a daily basis I was not programming, I was thinking about types and fighting with the compiler. And that is the language which has a pretty decent IDE plugin. When I moved to D, it felt like a breathe of fresh air to me. Therefore, the whole talk above about auto and types looks like subjective nitpicking. In practice though, D codes fast and runs fast, as promised on the official site.