Regards (From mobile) > On Jun 29, 2016, at 8:16 PM, Adrian Zubarev via swift-evolution > <[email protected]> wrote: > > I can’t resist I’ve got a third argument for your ‘scrolling’: Grab a huge > protocol that does not fit on your screen, which assistance do you have to > get its access modifier? >
Is this argument a translation for "look, the problem already exists, so it should really not matter that we make it worse"? > > > -- > Adrian Zubarev > Sent with Airmail > > Am 29. Juni 2016 um 20:03:31, Adrian Zubarev > ([email protected]) schrieb: > >> 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 > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
