Proposal: https://github.com/apple/swift-evolution/pull/213
On Wed, Mar 9, 2016 at 1:29 PM, Kevin Ballard via swift-evolution < [email protected]> wrote: > One minor change to what I've been proposing: Instead of merely saying > that it's implementation-defined, we should expressly say that invoking > next() after it has previously returned nil may return nil or it may return > an implementation-defined value, but it should not fatalError() (unless > some other GeneratorType requirement has been violated). Which is to say, > after a GeneratorType has returned nil from next(), it should always be > safe to invoke next() again, it's just up to the particular implementation > to determine what value I get by doing that. > > -Kevin Ballard > _______________________________________________ > 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
