Hi, James. I'm having trouble thinking of when I want to remove something from an array unless the array is empty. The one case I can think of is when an array is being treated as a stack or queue and you're popping in a loop, but I (personally) rather write that with an explicit isEmpty check anyway. (It's not like it's any more or less efficient.)
Is there another scenario that I'm missing where this would be useful? Thanks, Jordan > On Jan 6, 2016, at 9:36, James Campbell via swift-evolution > <[email protected]> wrote: > > If you call removeFirst and the array is empty it would be great if it was > optional so it could return nil or at least it threw an error so you could > handle that case. > > -- > Wizard > [email protected] <mailto:[email protected]> > +44 7523 279 698 > _______________________________________________ > 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
