> On Mar 17, 2016, at 11:23 PM, Charles Srstka via swift-evolution > <[email protected]> wrote: > > If you know something’s non-null, is there any advantage to keeping it in an > implicitly-unwrapped optional instead of a normal non-optional type? > > Charles Performance, in certain circumstances. If you’re about to pass it to something that’s expecting a `T?` or `T!` instead of just a `T`, you wouldn’t have to rewrap it first.
(Come to think of it, is there a cost to converting between `T?` and `T!`, or do they get optimized into the same thing?) - Dave Sweeris _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
