[swift-evolution] [pitch] "import" declaration, support for comma-separated modules

Jean-Denis Muys jdmuys at gmail.com
Tue Oct 18 03:10:02 CDT 2016

I don't agree with the line of reasoning that goes something like that:

"Event though you have <some legitimate reason>, I want to forbid every one
from using additive feature X because I don't like it, given <some other
legitimate reason>"

I also don't understand why this would impede qualified import syntax. What
is wrong with:

import func Framework.someMethod, func OtherFramework.someOtherMethod

So far for me this is +1.

Because additive, not in scope for phase 1 of Swift 4, though, as most of
the topics on this list recently.

On 18 October 2016 at 08:01, Georgios Moschovitis via swift-evolution <
swift-evolution at swift.org> wrote:

> > I'd almost always prefer to have another three lines of a
> protocolvisible, than three lines of imports.
> Maybe you just need an editor that can fold the imports (e.g. JetBrains)
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20161018/de9fffd3/attachment.html>

More information about the swift-evolution mailing list