This repository contains the scripts to answer the question: if NIO was to drop Swift 5.0 and 5.1, how many of its dependencies would be affected?
- original question: "Is anybody still using SwiftNIO or anything that uses SwiftNIO on Swift 5.0 or 5.1 in production?"
- https://twitter.com/_sa_s/status/1398286782807035910?s=21
- https://github.com/SwiftPackageIndex/nio-dependency-analysis
Steps to perform analysis:
- run
nio-analysis.swiftin the checkouts directory containing all package checkouts (copy from builder)- loop over package checkouts
- open
Package.resolvedto see if NIO is among the dependencies- if there is no
Package.resolved, runswift package dump-packagefirst
- if there is no
- log NIO-dependents
compatibility.sql- run SQL snippets to compile lists of packages compatible with certain Swift versions
playground.sql- copy in results from
nio-analysis.swiftintonioDependees - copy in results from
compatibility.sqlinto thecompatible_5_xconstants - run playground to compute the compatibility table
- copy in results from
