Extending availability to support library versioning would be a great proposal.
You should also take a look at the library evolution proposal, where this functionality will be required to implement the resilience model: https://github.com/apple/swift/blob/master/docs/LibraryEvolution.rst Slava > On Jan 18, 2017, at 4:24 PM, Swizzlr via swift-evolution > <swift-evolution@swift.org> wrote: > > Say I have an awesome type, and I provide some extensions that makes it work > really well with a few other packages. > > I don't want to force those packages on my users, but if they have them, I > want to extend them with my awesome type/function/whatever convenience. > > What can be done in code and package manager to weakly link (not literally, I > just mean have that behaviour) my awesome type with all these other libraries? > > This is a prelude to a pitch, if there isn't a decent alternative. > > Tom > > Sent from my iPhone > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
