If the deployment target was newer than the target that os_unfair_lock() became available deprecation warnings were generated for use of OSSpinLock. Now OSSpinLock isn't used if the deployment target is >= the OS version where os_unfair_lock() became available.

[papac25]

If the deployment target was newer than the target that os_unfair_lock() became available deprecation warnings were generated for use of OSSpinLock. Now OSSpinLock isn't used if the deployment target is >= the OS version where os_unfair_lock() became available.

New Pull Request Checklist

• [x] I have read and understood the CONTRIBUTING guide

• [x] I have read the Documentation

• [x] I have searched for a similar pull request in the project and found none

• [x] I have updated this branch with the latest master to avoid conflicts (via merge from master or rebase)

• [x] I have tested to prove the fix/feature I am adding

• [x] I have updated the documentation (if necessary)

• [x] I have run the lint and it passes (pod lib lint)

This merge request fixes / refers to the following issues: #3136

Pull Request Description

Fix deprecation warnings for OSSpinLock

If the deployment target was newer than the target that os_unfair_lock() became available deprecation warnings were generated for use of OSSpinLock. Now OSSpinLock isn't used if the deployment target is >= the OS version where os_unfair_lock() became available.

If you want to test this manually you can temporarily set the iOS Deployment target in the SDWebImage project to 11 or newer (and the same for the other OS targets) and build for iOS. In master you will get the deprecation warnings and in this PR branch the warning will not be present.

Originally posted by @phoney in https://github.com/SDWebImage/SDWebImage/pull/3137

[septs]

@jk234ert iOS ?

[Jack-Works]

Hmm, I'm confused, what is this?