[swift-build-dev] Namespacing SPM modules (was Re: [swift-dev] Right list?)
erica at ericasadun.com
Mon Feb 29 10:53:37 CST 2016
I'll try writing up a proposal. Does everything work the same for swift-build-dev as -evolution?
> On Feb 26, 2016, at 5:04 PM, Max Howell <max.howell at apple.com> wrote:
>> On Feb 26, 2016, at 3:17 PM, Erica Sadun <erica at ericasadun.com <mailto:erica at ericasadun.com>> wrote:
>> I think names like "Daniel Dunbar's String Extensions" is great when talking in English about a specific extension but I think the actual name should be as simple and elegant as possible without overlapping with built-in keywords.
> Yes, indeed, I meant as you think: when talking out loud about things we refer to the package as “Daniel Dunbar’s String Extension”, but in the code we would want:
> import StringExtensions
> or in the case of conflict:
> import ddunbar.StringExtensions
>> import org.sadun.StringUtilities // I can live with this but I'd rather import with a custom name established in dependencies
> Another reason I think to avoid being able to customize the import name is for consistency in the packaging community. We should be trying to establish recognizable names.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-build-dev