> * Are the current stdlib names for optional map and flatMap misleading?
Not so much misleading, as being unfortunate when optionals and collections end up as neighbors in the code. > * Are the current stdlib functions for optional closure application > appropriate and sufficient? > > public func f1<U>(@noescape f: (Wrapped) throws -> U) rethrows -> U? > public func f2<U>(@noescape f: (Wrapped) throws -> U!) rethrows -> U! > public func f3<U>(@noescape f: (Wrapped) throws -> U) rethrows -> Void I don't see why flatMap needs to be separate from map. It just does not make sense. I would only have public func f2<U>(@noescape f: (Wrapped) throws -> U?) rethrows -> U? and would call it "ifPresent", "then", "unwrap", "transform" or something like that. A.
_______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
