> On Jun 9, 2017, at 9:12 AM, Gor Gyolchanyan via swift-evolution > <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: > >> >> So I wonder if any of you have had any thoughts about what Swift's >> parentheses-related future (or evolutionary baggage) will be? >> > > I really wish swift used the concept of tuples **exclusively** for all > purposes that involve parentheses, as well as dividing tuples into two > categories: > - Bare tuples, which do not have labels. > - Rich tuples, which do. > As a consequence, here's a list of statements that would become true: > - All functions take exactly one parameter, which is a tuple. > - All closures (a.k.a. function pointers) take exactly one parameter, which > is a bare tuple.
A function would need to support a nonassignable, superset tuple in some cases such as: - non-escaping functions - inout parameters > - All functions return exactly one parameter, which is a tuple. Is or could be? Are you defining inout parameters as syntactically hidden return values? -DW
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
