Address build issues occurring when building with Library Evolution support, Xcode 16 #133
Conversation
Address build issues seen building for library evolution mode, Xcode 16 - i.e. `make build-for-library-evolution`.
gemmakbarlow
changed the title
gemmakbarlow
changed the title
gemmakbarlow
changed the title
gemmakbarlow
changed the title
| file: IssueContext.current?.filePath ?? filePath, | ||
| line: IssueContext.current?.line ?? line | ||
| ) | ||
| @unknown default: break |
There was a problem hiding this comment.
Do you think it's worth reporting issues from this branch? From a practical perspective I can't see this unknown branch ever hitting, though, so this should be OK.
There was a problem hiding this comment.
I definitely went back-and-forth about combining this with the nil branch case somehow. I ultimately came to the same conclusion you did; unlikely to fire in practice.
Oh that makes sense 😄 Awesome. |
|
@stephencelis - if you're able to cut a new release and update some of the other Happy to help with the effort if useful ! |
|
@gemmakbarlow Done! https://github.com/pointfreeco/swift-issue-reporting/releases/tag/1.4.1 There should be no need to change our other libraries to receive the update. Just make sure you update your packages in your project so that the Package.resolved file pulls in the newer version and you should be good to go! Or you can explicitly depend on 1.4.1 in your package/project. |
Perfect, thanks for the tip and speedy replies. |
Address build issues seen building for library evolution mode, Xcode 16 - i.e. via
make build-for-library-evolution.