Speaking of C++, is the “group” keyword even necessary? To borrow your own
example from earlier, it seems like we could just as easily say this:
public struct A {
public { // all public
func member1() {}
func member2() {}
func member3() {}
}
public labelName {// all public, accessible under `foo.lableName`
func member4() {}
func member5() {}
func member6() {}
}
}
(which is not C++’s syntax, I know… the comment just got me thinking about it
is all)
- Dave Sweeris
> On Jun 29, 2016, at 1:03 PM, Adrian Zubarev via swift-evolution
> <swift-evolution@swift.org> wrote:
>
> Looking at how c++ has a similar access modifier indent mechanism I’m still
> wondering if you’d argue about scrolling there.
>
> with no assistance to find where it is
> An assistant isn’t something the language solves for you. This is a different
> talk about the IDE. Grab some stdlib or foundation code and look at the
> filename and the code inside the file. The file might not contain only a
> single type equal to the filename. Also if there is another huge type present
> and you have a small display and currently looking at some specific member in
> the middle of that that type, which assistance have to find out the type of
> that member? Here we go again: you’re own assistant will your own negative
> argument ‘scrolling’.
>
>
>
>
> --
> Adrian Zubarev
> Sent with Airmail
>
> _______________________________________________
> swift-evolution mailing list
> swift-evolution@swift.org <mailto:swift-evolution@swift.org>
> https://lists.swift.org/mailman/listinfo/swift-evolution
> <https://lists.swift.org/mailman/listinfo/swift-evolution>
_______________________________________________
swift-evolution mailing list
swift-evolution@swift.org
https://lists.swift.org/mailman/listinfo/swift-evolution
