> On Jun 14, 2016, at 7:12 AM, L. Mihalkovic via swift-evolution > <swift-evolution@swift.org> wrote: > > > On Jun 14, 2016, at 11:31 AM, Patrick Smith via swift-evolution > <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: > >> Thanks Xiaodi. Interesting arguments there. It possibly seems a shame to me, >> because it has knock on effects of making other things more complicated. But >> I do see how for the most simple case of unwrapping a single Optional, it >> makes sense. >> >> As much as I would like Brent’s proposal to make things easier to type, I >> think nesting things inside a tuple, where a reader must keep track of which >> input matches which output, could lead to harder to follow code. > > Isomehow I think last yesterday's keynote should recast some expectations > about the degree of complexity (richness) the language will ever reach... > Somehow xamarin/c# might endupmbeing swift++ for many people
How so? What proposals might the core team accept that would confirm your suspicions; would this be one of them? Maybe I should drop Swift and move to C#, if that language is going to end up so much better than Swift in the future. It's never good to be tied down to a single language. Best, Austin
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
