<div dir="ltr">Well, indeed it looks like I’ve missed some important parts of the docs:<div><br></div><div>1. firstly it’s the doc for the Package manager which gives a brief intro to modules/packages/targets/dependencies</div><div><br></div><div>2. then there’s the Using the Build section (<a href="https://swift.org/getting-started/#using-the-build-system">https://swift.org/getting-started/#using-the-build-system</a>) which touches on the topics of source organization (basically it mentions a Sources directory and the main.swift files)</div><div><br></div><div><br></div><div>:- alex</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Feb 6, 2016 at 8:44 PM, alex <span dir="ltr"><<a href="mailto:themindstorm@gmail.com" target="_blank">themindstorm@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>My apologies if I missed this information, but my searches came out empty on both these topics:</div><div><br></div><div>1. is there a recommended project organization/structure? (most of the languages I’m familiar with have either a recommended or even impose a specific project structure).</div><div><br></div><div>2. The Swift grammar mentions imports, but I couldn’t find any reference on how do declare packages or modules or any high level namespace groupings that the language supports (if any)</div><div><br></div><div><br></div><div>thanks,</div><div><br></div><div>:- alex</div></div>
</blockquote></div><br></div>