> Having one import per line is much more readable and maintainable

This depends on how much importance you give to "import" declarations. If
you feel they equally important as the rest of your code, I can understand
why you would want to see them. I don't.

My preference is to see as much of the rest of my code as possible. I don't
spend nearly as much time checking which modules I imported, as I do
editing functions and classes. I'd almost always prefer to have another
three lines of a protocol visible, than three lines of imports. Except that
the imports will be visible anyways, just - and even this is arguable in
many cases - harder to read.

> I never understood the desire for *extreme* vertical conciseness

It's probably *because* I use more vertical space than most people, that
losing screen real-estate to "import" declarations bothers me.


On Mon, Oct 17, 2016 at 8:40 AM, Said Sikira via swift-evolution <
swift-evolution@swift.org> wrote:

> -1. I disagree.
>
> Having one import per line is much more readable and maintainable
> especially when you have statements like `import func Framework.someMethod`.
>
> Being able to use `let a, b, c, …` doesn’t have to do anything with
> importing modules since those are completely different features of the
> language.
>
> On October 17, 2016 at 5:22:02 PM, Jay Abbott via swift-evolution (
> swift-evolution@swift.org) wrote:
>
> -1 - I don't like this.
>
> I never understood the desire for *extreme* vertical conciseness, it tends
> to make code less readable in general and definitely makes diffs a lot
> harder harder to read.
>
>
> On Sun, 16 Oct 2016 at 11:26 Anton Zhilin via swift-evolution <
> swift-evolution@swift.org> wrote:
>
>> Purely additive feature, not for Swift 4 Phase 1.
>> And a -1 from me for reasons already mentioned.
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution@swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution@swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution
>
>
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution

Reply via email to