Fix locking in requests, os_unfair_lock not to be directly used in Swift #429
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
os_unfair_lock should not be used directly in Swift as it doesn't have a stable memory address, see https://developer.apple.com/documentation/os/osallocatedunfairlock. We can't yet use OSAllocatedUnfair lock due to our deployment target, but we can force os_unfair_lock to heap allocate and then use it safely.
Inspired by HA: https://github.com/home-assistant/HAKit/blob/main/Source/Internal/HAProtected.swift