[swift-evolution] [Review] SE-0159: Fix Private Access Levels
jhull at gbis.com
Mon Mar 27 02:17:33 CDT 2017
> On Mar 26, 2017, at 9:37 PM, Charles Srstka <cocoadev at charlessoft.com> wrote:
>> On Mar 26, 2017, at 11:21 PM, Jonathan Hull via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> I wonder if there is a different type of UI solution which might help people who hate dividing things up into lots of small files.
>> I find the way that I work is to make a super large file while I work, and then break it down into smaller files once the main design is in place and has settled. I find one file easier while things are in flux, but many (well grouped) small files easier for reference and maintenance.
>> If you have used programs like Ulysses or Scrivener, they allow you to select multiple sections/files and then those sections show one after another in the editing UI with a divider between them.
>> I know we don’t have control over Xcode here, but we could certainly recommend such a feature to those who do. Basically, if you select a group (or multiple files), it would show the contents of each file placed in order so you could edit across them.
>> Would something like that help? (I am mainly trying to get a sense of the underlying goals of those on both sides of this argument).
> For your tiny helper type, you want it to be only visible to the type it helps. If it’s in a separate file, it has to be visible to the entire module.
Then you could keep it in the same file. As you said, the helper type is tiny.
(or once we have submodules, I suppose you could put it somewhere else in the submodule, if desired)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution