Re: [swift-evolution] [Draft] scope-based submodules

> On Mar 3, 2017, at 12:56 PM, Matthew Johnson wrote: > >> Outside the `WorldOptimization` module, of course, you'd still need to write >> `import WorldOptimization.SpimsterWicket` to get access to the `WicketShell` >> type. (Or perhaps importing `WorldOptimization`

Re: [swift-evolution] [Draft] scope-based submodules

> On Mar 2, 2017, at 10:08 PM, Brent Royal-Gordon > wrote: > >> On Mar 1, 2017, at 11:56 AM, David Hart wrote: >> >>> 2. Normally, references within the module to submodule symbols need to be >>> prefixed with the submodule name. (That is, in

Re: [swift-evolution] [Draft] scope-based submodules

> On Mar 1, 2017, at 11:56 AM, David Hart wrote: > >> 2. Normally, references within the module to submodule symbols need to be >> prefixed with the submodule name. (That is, in top-level `Foo` code, you >> need to write `Bar.Baz` to access `Foo.Bar.Baz`). As a convenience,

Re: [swift-evolution] [Draft] scope-based submodules

> On Mar 1, 2017, at 1:56 PM, David Hart wrote: > > Wonderful comments. I really enjoy your take on submodules which keeps most > of the power while keeping the simplicity. Comments below: > > > Sent from my iPhone > > On 1 Mar 2017, at 07:55, Brent Royal-Gordon via

Re: [swift-evolution] [Draft] scope-based submodules

> On Mar 1, 2017, at 12:55 AM, Brent Royal-Gordon > wrote: > >> On Feb 24, 2017, at 11:34 AM, Matthew Johnson via swift-evolution >> wrote: >> >> Scope-based submodules >> >> • Proposal: SE- >> • Authors: Matthew Johnson >>

Re: [swift-evolution] [Draft] scope-based submodules

Wonderful comments. I really enjoy your take on submodules which keeps most of the power while keeping the simplicity. Comments below: Sent from my iPhone On 1 Mar 2017, at 07:55, Brent Royal-Gordon via swift-evolution wrote: >> On Feb 24, 2017, at 11:34 AM,

Re: [swift-evolution] [Draft] scope-based submodules

> On Feb 24, 2017, at 11:34 AM, Matthew Johnson via swift-evolution > wrote: > > Scope-based submodules > > • Proposal: SE- > • Authors: Matthew Johnson > • Review Manager: TBD > • Status: Awaiting review Well, this is certainly

Re: [swift-evolution] [Draft] scope-based submodules

> On Feb 24, 2017, at 4:57 PM, David Hart wrote: > >> >> On 24 Feb 2017, at 20:34, Matthew Johnson via swift-evolution >> > wrote: >> >> I didn't expect submodules to be a part of the Swift 4 discussion. When it

Re: [swift-evolution] [Draft] scope-based submodules

> On 24 Feb 2017, at 20:34, Matthew Johnson via swift-evolution > wrote: > > I didn't expect submodules to be a part of the Swift 4 discussion. When it > came up I was pleasantly surprised. I have been thinking about the design of > a submodule system for quite a

Re: [swift-evolution] [Draft] scope-based submodules

> On Feb 24, 2017, at 3:56 PM, Vladimir.S wrote: > > Matthew, thank you for sharing this great text! > Unfortunately was not able to read it in details yet, but after looking for > proposed solution, have a quick question. Thanks for taking a look! I’m looking forward to

Re: [swift-evolution] [Draft] scope-based submodules

Matthew, thank you for sharing this great text! Unfortunately was not able to read it in details yet, but after looking for proposed solution, have a quick question. You are proposing to have 'submodule' keyword in each file of that submodule. How can we then solve such issue: imagine that I

[swift-evolution] [Draft] scope-based submodules

I didn't expect submodules to be a part of the Swift 4 discussion. When it came up I was pleasantly surprised. I have been thinking about the design of a submodule system for quite a while but was planning to wait until it was clearly in scope to draft a proposal. Now that the topic has been