Closed clackary closed 11 months ago
Let me know if this issue belongs over in swift-case-paths, but since the workaround can be applied in swift-parsing (or also in whatever package includes swift-parsing), I figured it makes sense to file here.
@clackary We run CI against Swift 5.9.1, so I don't think this is an issue with the library so much as an issue with development snapshots needing to explicitly enable certain feature flags. If you can reproduce this with an official release and share the repro, please do! Till we can determine this is a bug in the library I'm going to convert it to a more general discussion.
After digging a bit, this is mostly a heads up that a new compiler error in recent toolchains, possibly as early as 5.9.1, seems to break
swift-case-paths
build.To reproduce:
swift-DEVELOPMENT-SNAPSHOT-2023-10-02-a
, but I'm guessingswift-5.9.1-RELEASE
would likely also reproduce)swift-case-paths
to something from 1.1.0 -.package(url: "https://github.com/pointfreeco/swift-case-paths", from: "1.1.0"),
swift build
Workaround:
swift-case-paths
to 1.0.0 -.package(url: "https://github.com/pointfreeco/swift-case-paths", exact: "1.0.0"),