[swift-evolution] Proposal: CollectionType.cycle property for an infinite sequence
devteam.codafi at gmail.com
Tue Dec 29 22:58:50 CST 2015
I think we have to make some things clear. Unfortunately, I used the word stream when I meant cycle, they are very different things from an implementer's perspective. A stream is a generalized version of a cycle, where the latter admits infinite sequences of any kind or mix of data (say, the Fibonacci example here), the latter admits only infinite representations based on an initial finite input. This makes many divergent cases in the former perfectly valid in the latter through proper manipulation of an underlying finite sequence. If you want to see what a Cycle looks like, Rust has std::iter::Cycle. Swiftz, on the other hand, shows what a proper stream would look like (and having written the thing, I do not wish to see support for it in the Swift Standard Library).
2015/12/29 18:39、Craig Cruden <ccruden at novafore.com> のメッセージ:
> I have never tried to implement a “stream” in Swift, so I am not sure if there is an easy way to do it…. but I don’t see a collection of type stream as I have in Scala.
>>> On 2015-12-30, at 7:39:54, Dave Abrahams <dabrahams at apple.com> wrote:
>>>> On Dec 29, 2015, at 4:29 PM, Craig Cruden <ccruden at novafore.com> wrote:
>>>> Could you define what you mean by “stream support?” Whatever it is, I doubt simply adding an infinitely-repeating sequence type is enough to get you there.
>>> I can guess ― but it is only a guess.
>>> A function defines an infinite “set” of values (like the digits of pi). A stream is just a special type of traversable (lazy) which does not evaluate until asked for the next in a sequence of the set. A function defined in a stream will thus only continue calculating next digits when asked for them. Similarly you could have a collection (head/tail) and you ask for the head and you get it, but the rest (tail) is just the tail as a whole and none of the values in it are really defined until you traverse down to the next head of the rest of the tail. Once it is evaluated it is stored in memory for future evaluations. If you were to fully evaluate the function it would never finish, and if it were to finish ― you would probably run out of memory.
>> Yes, I understand the usual concept of a “stream," but it doesn’t help me understand what stream *support* entails.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution