If you're using Xcode, you can option-click a variable and (if Xcode's indexing is working, which is not a certainty) it'll show you the inferred type for that variable. This can help when looking at some new code and trying to figure out what all the bits really are.
Re:Go Home Swift Compiler, You’re Drunk
by geophile on Wednesday April 27, 2016 @02:00PM
(#11582860)
Yeah, I know, but it's been unreliable.
Re:Go Home Swift Compiler, You’re Drunk
by mpweiher on Wednesday April 27, 2016 @02:53AM
(#11578333)
In fact, this documentation effect is the only positive effect of static typing that has actual scientific support, unlike the supposed and oft-claimed safety/correctness benefits.
So while type-inference is a neat idea in theory, maybe it's not such a good idea in practice.
Re:Go Home Swift Compiler, You’re Drunk
by geophile on Wednesday April 27, 2016 @02:04PM
(#11582903)
I'm not sure why you say the safety/correctness benefits are not real. In a large code base, with multiple developers, it is easy to get someone misusing a function, passing one type when a different one is expected. I know that some people in the python world recommend unit testing to guard against this sort of thing, but to me, that is a poor substitute for static type checking.
(But at least each expression has a type. While I love Python and have used it for many years, I don't like the uncertainty about types.)