Error about constructor calls in loops/labels, but there are no loops and labels?

[Yuxuan Shui]

> I've been using Swift in the past few years quite a bit, and it 
> always amuses me when it can't figure out some kind of 
> inference that seems trivial, but it just gives up because the 
> compiler takes too long to determine: "This [one line] 
> statement is too difficult, please split into multiple 
> statements." This is the kind of stuff you would be 
> encountering.

Clarification to my last point. I'm saying Swift's compiler is 
not smart enough, because other type inference languages doesn't 
seem to have this weird limitation. Worst case is they can't 
infer the type, then they fail back to not inferring, which is 
not worse than not having type inference.

>
> -Steve