> Swift’s type system is best described as “way better than Java’s”, or perhaps “far more comprehensible than Scala’s”
I love Scala's type system, so I'm looking to seeing if Swift's really is better. Any type system is better than none at all - probably why most javascript-heavy apps become nightmares when they get to be > 1000 LOC.
For tiny things, I profoundly disagree. A great type system is still (IMO) better than none at all, but there are plenty of type systems that get in the way more than they can be pressed into helping especially when things are tiny. When things are large, it's there are probably still some pathologically unhelpful type systems, but there's generally more leverage to be had...
Having named parameters with different public than internal names is a brilliant idea, but I wonder how often it'll be used in practice. If it's used a lot, it might indicate that those parameters are badly named to begin with :)
I love Scala's type system, so I'm looking to seeing if Swift's really is better. Any type system is better than none at all - probably why most javascript-heavy apps become nightmares when they get to be > 1000 LOC.