-
-
Notifications
You must be signed in to change notification settings - Fork 532
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nuke 13 – Swift 6 #802
base: main
Are you sure you want to change the base?
Nuke 13 – Swift 6 #802
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lots of detailed updates and thank you Alexander for adding this full swift6 support.
@@ -4,11 +4,11 @@ | |||
|
|||
import Foundation | |||
|
|||
final class Atomic<T>: @unchecked Sendable { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume that it would be good to take Mutex backport implementation from swift-sharing
framework, which is ported from Swift.Synchronization
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, interesting. Thanks for the link. I'll look into it.
Requirements
Changes
ImagePipelineActor
Nuke has been designed around the global actor pattern for quite a while now, so it was an easy change to introduce a global
ImagePipelineActor
as a replacement.ImagePipeline
,ImagePrefetcher
,ImageTask
, and allAsyncTask
implementations are now syncrhonized on the new actor instead of a a serial GCD queue.