<div style="white-space:pre-wrap">The issue of Void and () has definitely been brought up before.<br></div><br><div class="gmail_quote"><div dir="ltr">On Sun, Jul 3, 2016 at 15:04 Haravikk via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On 3 Jul 2016, at 20:03, Vladimir.S <<a href="mailto:svabox@gmail.com" target="_blank">svabox@gmail.com</a>> wrote:<br>
><br>
> 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" ?<br>
<br>
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?<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>