[swift-evolution] [RFC] "Library Evolution Support in Swift ('Resilience')"

Drew Crawford drew at sealedabstract.com
Wed Feb 10 20:08:42 CST 2016

> I think the solution is that you shouldn't mark security-critical code as being eligible for inlining. Anything else is just not going to be workable.

There is no such thing as "I solemnly swear this function doesn't have a security bug, and if it does, we'll never patch it."

If we have to choose between security and inlining, let's not allow inlining across versioned APIs.

More information about the swift-evolution mailing list