I totally sympathize with users being confused. It's an interesting idea to move it to Array only.
The thing is, it does make sense (and wouldn't be confusing) to enumerate a dictionary or set. Moreover, the behavior is _exactly_ what it says on the tin: when you enumerate something in real life, there is no sense in which the number is related to some sort of index. Can we fix this by documentation? Like, a big blaring "don't use this when you want the index"? On Tue, Jan 31, 2017 at 09:35 Ole Begemann via swift-evolution < [email protected]> wrote: > On 31/01/2017 16:19, Ole Begemann via swift-evolution wrote: > > Here are three previous discussion about this topic: > > > > 1) December 2015: [Idea] Add an (Index, Element) sequence to > > CollectionType > > > https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151221/004561.html > > and > > > https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20151228/004626.html > > > > > > 2) April 2016: [Idea] Replace enumerate() with something more explicit > > > https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160411/015074.html > > > > > > 3) September 2016: [Proposal draft] Introducing `indexed()` > collections > > > https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20160926/027355.html > > To clarify, the discussions I linked to don't all propose to remove or > replace `enumerated()`, but they all talk about the potential confusion > about what `enumerated()` does and does not do. > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution >
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
