> Probably not, The name is a strawman. I guess I could not resist the > optimizer speak after all. The programmer is asserting he guarantees the > lifetime by other means. I expect if this proposal moves forward the standard > library team will decide on the right name for this method. > > assertLifetimeGuarantee, withAssertedLifetime, > unsafePassWithAssertedLifetime, ... ?
withUnsafeUnownedValue? I think that conveys the danger—you've been passed a value which you don't own, so something else had better keep it alive—even if it's not technically accurate. -- Brent Royal-Gordon Architechies _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
