+1<br><br>2016年10月16日日曜日、Rien via swift-evolution<<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>>さんは書きました:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Specifically, I don’t care much. Say -0.1 :-)<br>
<br>
In general I am against “savings lines”.<br>
While very short modules (< 10) do indeed profit from having fewer lines, most modules don’t.<br>
Having a few more lines, even empty ones, can do a lot to improve code readability imo.<br>
Probably my Ada experience showing through….<br>
<br>
Rien.<br>
<br>
> On 16 Oct 2016, at 02:41, Charles Constant via swift-evolution <<a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')">swift-evolution@swift.org</a>> wrote:<br>
><br>
> How would we all feel about allowing multiple modules with one import statement?<br>
><br>
> Eg: the option to write<br>
><br>
> import Cocoa, Foo, Bar.Baz<br>
><br>
> in addition to just:<br>
><br>
> import Cocoa<br>
> import Foo<br>
> import Bar.Baz<br>
><br>
> When I'm writing smaller files that import a few modules, I'd prefer to lump the imports together like this. Doesn't seem like a feature that would require much effort to implement either.<br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> swift-evolution mailing list<br>
> <a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')">swift-evolution@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
<br>
______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="javascript:;" onclick="_e(event, 'cvml', 'swift-evolution@swift.org')">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
</blockquote>