Deprecate dispatch_main_async_safe, introduce two more policy `.safeAsyncMainThread` (for UIKit diffable data source) and `.safeAsyncMainQueue` (for most common cases) by dreampiggy · Pull Request #3766 · SDWebImage/SDWebImage

Skip to content

Navigation Menu

Sign in

Appearance settings

Conversation

…SDCallbackQueue and may callback in non-main queue
…for UI-related code logic

Handled two cases in real-world app
This used for user who really need `mainThread` but not `mainQueue`

@dreampiggy dreampiggy changed the title Deprecate dispatch_main_async_safe, UIView+WebCache API now supports SDCallbackQueue and may callback in non-main queue Deprecate dispatch_main_async_safe, introduce two more policy .safeAsyncMainThread and .safeAsyncMainQueue for different use case

Nov 14, 2024
…e `SafeAsyncMainQueue`, others revert back to default value

The implementation don't need complicated check, using object compare is enough

@dreampiggy dreampiggy changed the title Deprecate dispatch_main_async_safe, introduce two more policy .safeAsyncMainThread and .safeAsyncMainQueue for different use case Deprecate dispatch_main_async_safe, introduce two more policy .safeAsyncMainThread and .safeAsyncMainQueue for different use case, and defaults to MainThread

Nov 15, 2024

@dreampiggy dreampiggy changed the title Deprecate dispatch_main_async_safe, introduce two more policy .safeAsyncMainThread and .safeAsyncMainQueue for different use case, and defaults to MainThread Deprecate dispatch_main_async_safe, introduce two more policy .safeAsyncMainThread (for UIKit diffable data source) and .safeAsyncMainQueue (for most common cases)

Feb 20, 2025

This was referenced

Feb 20, 2025

Labels