> On Dec 20, 2017, at 10:34 PM, Slava Pestov via swift-evolution > <swift-evolution@swift.org> wrote: > >> Perhaps a diagnostic like this would cause problems if you started with an >> @inlinable function that called an @abiPublic function and then in a >> subsequent version of your module you modified the @inlinable function such >> that it no longer calls the @abiPublic function. You would still need to >> keep that @abiPublic function to support clients that had inlined the old >> version, right? > > This is correct; you may well end up with newer versions of a library that > carry @abiPublic symbols only for compatibility reasons.
Perhaps an “unused symbol checker” could skip @abiPublic declarations that have been marked as deprecated or unavailable. Slava
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
