[Second review] SE-0516: `Iterable`

? Not sure that I specifically have anything to say about this.

Fundamentally, we need a distinct name for the associated type and its corresponding protocol. It would not make it better if there were some last-ditch disambiguation syntax. We would never want to assign the same name to two distinct things that we can readily anticipate will clash like this.

The sum total of options that I can see are:

  • Naming the new thing after Iterable (i.e., IterableIterator)—as proposed.
  • Naming the new thing after "how it achieves what it is" instead of "what it is" (e.g. SpanIterator)—our general approach is to avoid naming things by the "how" instead of the "what."
  • Naming the new thing with some description of the ways in which "what it is" differs from the old thing—this starts to blur with the previous approach and often ends up being too reductive (thus possibly misleading) and/or too wordy: we want a name and not a description.
  • Naming the new thing Iterator2.