Don't depend on DispatchQueue's Equatable conformance #311
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
Fix issue with `ifLet` where `else` was being called too often (#225)
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.
Among the changes I had to make in order to get the ReactiveSwift fork building for Linux was not depending on the
Equatableconformance ofDispatchQueue, and I realised that it probably isn't necessary at all.Equatableconformance allows theswitch selfand the matching on.main, however, in LinuxDispatchQueuedoes not conform toEquatable, so this doesn't work.Since for the other queues we are doing name matching we could do the same for
.mainwhose name is always"com.apple.main-thread"