I believe rather than being an issue with swift-syntax in particular, this is probably just yet another symptom showing why SwiftPM should either get a bit more clever with dependency resolution (by ignoring clashing dependencies that are never used together; probably easier said than done), or allowing dependencies to be renamed. I’ve often run into the same issue with swift-argument-parser in particular, which is always quite annoying because I know it’s only being used in executable targets upstream and wouldn’t actually cause any issues.
14 Likes