Updating swift-case-paths - EnumReflection.swift:87:74: error

[oschrenk]

I'm trying to compile an older application of mine using and now get

I see that swift-case-paths is pulling 1.0.0 version, and I hope that 1.7.2 might resolve the issue below

/Users/oliver/Projects/personal/swift/plan.swift/.build/checkouts/swift-case-paths/Sources/CasePaths/EnumReflection.swift:87:74: error: conflicting arguments to generic parameter 'T' ('(UInt32?, (Bool, any Any.Type)?)' vs. '(UInt32?, (isIndirect: Bool, associatedValueType: any Any.Type)?)')
 85 |     let rootTag = metadata.tag(of: root)
 86 |
 87 |     if case let (cachedTag?, (isIndirect, associatedValueType)?) = cache.withLock({
    |                                                                          `- error: conflicting arguments to generic parameter 'T' ('(UInt32?, (Bool, any Any.Type)?)' vs. '(UInt32?, (isIndirect: Bool, associatedValueType: any Any.Type)?)')
 88 |       ($0.tag, $0.strategy)
 89 |     }) {
/Users/oliver/Projects/personal/swift/plan.swift/.build/checkouts/swift-case-paths/Sources/CasePaths/EnumReflection.swift:87:74: error: conflicting arguments to generic parameter 'T' ('(UInt32?, (Bool, any Any.Type)?)' vs. '(UInt32?, (isIndirect: Bool, associatedValueType: any Any.Type)?)')
 85 |     let rootTag = metadata.tag(of: root)
 86 |
 87 |     if case let (cachedTag?, (isIndirect, associatedValueType)?) = cache.withLock({
    |                                                                          `- error: conflicting arguments to generic parameter 'T' ('(UInt32?, (Bool, any Any.Type)?)' vs. '(UInt32?, (isIndirect: Bool, associatedValueType: any Any.Type)?)')
 88 |       ($0.tag, $0.strategy)
 89 |     }) {

❯ swift --version
swift-driver version: 1.127.14.1 Apple Swift version 6.2.1 (swiftlang-6.2.1.4.8 clang-1700.4.4.1)
Target: arm64-apple-macosx26.0

[stephencelis]

@oschrenk This isn't a strict requirement, and you should be able to bump CasePaths from your project in Xcode or via SPM on the command line. Have you tried right-clicking on the package from Xcode to update it?

Since this isn't a bug with the library I'm going to convert to a discussion.

[oschrenk]

Thanks. I now manually overwrote the transitive dependency version in my Package.swift

I hope other people wanting to use this library know more about Swift, language and culture, than I do. Coming from JVM world the libraries and dependencies seem much more fragile and dependent on language/dependency changes.