> On 3 Jul 2016, at 20:03, Vladimir.S <[email protected]> wrote: > > But, then, regarding the consistency and confusion, I have a question: is it > expected that func f() {..} will *return* `Void` ? I believe it is not > expected exactly at the same level as Void in parameter for 0 argument > function. I.e. should `-> ()` still means "returns Void" or "returns nothing" > ?
Fair question, personally I never use () to indicate void on the return side, and always specify the return type, so there's never any doubt what I meant, but that's just convention at the moment. I wouldn't mind seeing one style of void return being forced for consistency, but that's probably out of scope for this issue. It seems vaguely familiar though, has an issue already come up about removing the redundancy? _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
