I think this is closely related to the thread about “Non-Standard Library”. If we had a CocoaPods-like hub for libraries, this could trivially be added to it for people who think it’s worth it. Then we could discuss if the feature is worth including with Swift distributions, but that discussion could be based on real-world usage data and experience. And not including it would still mean that anyone could trivially install the feature as an external dependency. Which is still easily possible today, just the discoverability isn’t stellar.