Enable upcoming compiler features#401
Conversation
|
@FranzBusch removing @preconcurrency in a package supporting 6.0+ is not really a breaking change, or do I miss something? |
| settings.append(.enableUpcomingFeature("NonisolatedNonsendingByDefault")) | ||
|
|
||
| // Ensure all public types are explicitly annotated as Sendable or not Sendable. | ||
| settings.append(.unsafeFlags(["-Xfrontend", "-require-explicit-sendable"])) |
There was a problem hiding this comment.
We can't do this since unsafe flags are not allowed in SemVer stable packages
There was a problem hiding this comment.
That's not true anymore since 6.2 swiftlang/swift-package-manager#8951 / https://forums.swift.org/t/pitch-disable-checks-for-unsafe-flags-in-swiftpm/80698/27 so if we wanted to we could do so in Package+6.2
There was a problem hiding this comment.
I've added Package@swift-6.1.swift without the .unsafeFlags and the Package.swift now has .unsafeFlags.
There can be other packages that depend on the that have not yet migrated to Swift 6 language mode which would break if we remove the |
56969be to
142f05c
Compare
sync wi th other packages
0a6f96a to
bc66103
Compare
Enable several upcoming compiler features to make the codebase more explicit in intention:
Motivation:
Sync codebase with the modern practice, get ready for the upcoming features.
Modifications:
LoggingSystemmarked asSendableResult:
Codebase is updated with the modern practices.