For what it’s worth, I renamed OrderedSet to SortedSet in the Swift 3 version of BTree, so the original instance of this issue is hopefully no more.
Prohibiting modules from containing a symbol of the same name would require a mass renaming of many microframeworks. Besides BTree, I also have BigInt, Deque and RedBlackTree; I know Rob Rix has Result, Box, Either, Memo, Delay, Stream, BinaryTree, etc.; and there are oodles more. Renaming them is certainly doable, but it definitely would be a pain in the neck for everyone involved. I’m not even sure what naming convention we should use: most of these packages essentially consist of the type that they’re named after, and naming them like this was the most obvious option. (These names work well at the point of use, too: you want to use Result, so you need to import Result). Requiring/allowing reverse DNS-style module names (e.g. com.apple.Foundation) would be one way to solve the naming issue, but this seems hard to incorporate into the language at this point.) I’d much prefer having “import Foo as Bar” as a (hopefully) easy-to-implement stop-gap solution than to give up on these nice microframework names. This would not break existing code. I like the idea to allow absolute naming to resolve ambiguous names, but using _ for the root symbol seems very different to its usual meaning. Perhaps it's worth spending the # character on this: #.BTree.OrderedSet<Int>. Or how about "<>.BTree.OrderedSet<Int>”? None of these would be intuitively clear to read, though (and they need special magic to make sure a “<root>.BTree.” prefix is resolved to mean the module, not the struct.). If nested modules are in the cards for a future Swift, not having a delimiter at the end of the module path could become an issue. What if we allowed type expressions like “(OrderedSet<Int> in BTree)” or “(OrderedSet<Foo> from Foundation)”? The swapped order sure is strange though, and I have no idea if such a construct would fit in the grammar. But at least the meaning of it is reasonably clear, and the same scheme could also support the extension method case: e.g., "foo.(bar in MyModule)()”. C# has a somewhat similar issue with its namespaces: https://blogs.msdn.microsoft.com/ericlippert/2010/03/09/do-not-name-a-class-the-same-as-its-namespace-part-one/ <https://blogs.msdn.microsoft.com/ericlippert/2010/03/09/do-not-name-a-class-the-same-as-its-namespace-part-one/>. They have "global::” to refer to their root namespace, and they discourage (but not prohibit) naming a class the same as its enclosing namespace. I think Java's concept of obscured names is also relevant, but I’ll leave it to someone else to decipher the specification. :-) -- Karoly @lorentey > On 2016-07-17, at 01:07, Félix Cloutier via swift-evolution > <swift-evolution@swift.org> wrote: > > There is a lot of potential for it to be a breaking change. Currently, you > can do module qualification with Module.Symbol. This causes problems. The two > most obvious solutions (change the "operator" between Module and Symbol, or > prevent symbols from having the same name as their module) are breaking > changes. > > Félix > >> Le 16 juil. 2016 à 16:01:28, David Hart <da...@hartbit.com >> <mailto:da...@hartbit.com>> a écrit : >> >> I don't see anything source breaking here. I'm fairly sure it's 100% >> additive and will therefore wait for after Swift 3. >> >> On 17 Jul 2016, at 00:19, Félix Cloutier via swift-evolution >> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: >> >>> There is about 2 weeks left for source-breaking proposals, and this is >>> going to be one of them. How is progress going? Do you think that you'll >>> have enough time to push it out of the door? >>> >>> Félix >>> >>>> Le 20 juin 2016 à 17:33:03, Paulo Faria <pa...@zewo.io >>>> <mailto:pa...@zewo.io>> a écrit : >>>> >>>> Yeah! I’m working on a formal proposal that would solve the same problem. >>>> Jordan, the problem he described is exactly like the one you explained to >>>> me, haha. Now I’m a bit confused about how the proposal should be called. >>>> Have any suggestions? What title could fit the two use cases we mentioned. >>>> By the way, can you see any other use case that would be solved with the >>>> same solution? >>>> >>>> >>>>> On Jun 20, 2016, at 9:25 PM, Jordan Rose <jordan_r...@apple.com >>>>> <mailto:jordan_r...@apple.com>> wrote: >>>>> >>>>> I've been encouraging Paulo Faria to mention this case in his push for a >>>>> way to disambiguate extension methods, with the thought being we could >>>>> then use the same syntax to differentiate top-level names as well. >>>>> >>>>> I'd also be happy with the "import as" syntax. The underscore syntax >>>>> seems a little opaque, but I suppose it wouldn't come up very often. >>>>> >>>>> Jordan >>>>> >>>>> >>>>>> On Jun 17, 2016, at 19:52, Félix Cloutier via swift-evolution >>>>>> <swift-evolution@swift.org <mailto:swift-evolution@swift.org>> wrote: >>>>>> >>>>>> Hello all, >>>>>> >>>>>> I recently ran into a bug <http://stackoverflow.com/q/37892621/251153> >>>>>> that leaves me unable to fully-qualify the name of a type. If you import >>>>>> a module named Foo that also contains a type named Foo, attempts to >>>>>> fully-qualify any name in the Foo module will instead attempt to find >>>>>> something inside the Foo type. This bug has already been reported >>>>>> <https://bugs.swift.org/browse/SR-898>. >>>>>> >>>>>> Here's an example with Károly Lőrentey's BTree module (which also >>>>>> contains a BTree type) that I encountered while trying to use the >>>>>> OrderedSet type: >>>>>> >>>>>> let set = OrderedSet<Int>() >>>>>> // error: 'OrderedSet' is ambiguous for type lookup in this context >>>>>> // Found this candidate: Foundation.OrderedSet:3:14 >>>>>> // Found this candidate: BTree.OrderedSet:12:15 >>>>>> To solve this, you would normally write BTree.OrderedSet, but now Swift >>>>>> thinks that BTree is the BTree type, not the BTree module: >>>>>> >>>>>> let set = BTree.OrderedSet<Int>() >>>>>> // error: reference to generic type 'BTree' requires arguments in <...> >>>>>> Any fix will require a change to the language, and as Jordan Rose stated >>>>>> on the bug, it "needs design", so I would like to bring up the issue and >>>>>> discuss possible solutions. >>>>>> >>>>>> I can see several options (leaving "do nothing" aside, since I believe >>>>>> that this needs to be resolved): >>>>>> >>>>>> Prevent modules from containing a type with the same name >>>>>> Allow modules to be imported under different names (`import BTree as >>>>>> BTreeModule`, `import BTreeModule = BTree` or any similar syntax) >>>>>> Create a new syntax that indicates that you're naming a module, not a >>>>>> type (like `_.BTree.OrderedSet`) >>>>>> >>>>>> Thoughts? >>>>>> >>>>>> Félix >>>>>> >>>>>> _______________________________________________ >>>>>> swift-evolution mailing list >>>>>> swift-evolution@swift.org <mailto:swift-evolution@swift.org> >>>>>> https://lists.swift.org/mailman/listinfo/swift-evolution >>>>>> <https://lists.swift.org/mailman/listinfo/swift-evolution> >>>>> >>>> >>> >>> _______________________________________________ >>> swift-evolution mailing list >>> swift-evolution@swift.org <mailto:swift-evolution@swift.org> >>> https://lists.swift.org/mailman/listinfo/swift-evolution >>> <https://lists.swift.org/mailman/listinfo/swift-evolution> > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
