+1 On 31 January 2017 at 11:32, Russ Bishop via swift-evolution < [email protected]> wrote:
> > On Jan 30, 2017, at 5:55 AM, Tuur Anton via swift-evolution < > [email protected]> wrote: > > The lack of namespaces is making people create all kinds of "design > patterns". > > > What do you think? > > > I’ve used languages with namespaces for many years. I don’t find > multi-level namespaces to be much of an improvement over a single-level > namespace in most cases. On the contrary, I find it much simpler to avoid > hunting around importing a hundred namespaces. This is what you end up with: > > using System; > using System.Collections.Generic; > using System.Linq; > using System.Runtime.Serialization; > using System.ServiceModel; > using System.ServiceModel.Web; > using System.Text; > using System.Data; > using System.Data.SqlClient; > using System.Web; > using System.Net; > using System.Net.HttpClient; > > > > The only thing we really need in Swift is the ability to have a Private > submodule, especially for mixed-mode frameworks. > > > Russ > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution > > -- *Pranshu Goyal* *iOS Developer* *tlkn*
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
