Remove deprecation warnings from synchronous polling expectations - #4
Merged
acecilia merged 1 commit intoAug 10, 2026
Merged
Conversation
PR Quick#1199 added @available(*, deprecated) annotations to all synchronous polling functions (toEventually, toEventuallyNot, toNotEventually, toNever, neverTo, toAlways, alwaysTo, waitUntil). These functions continue to work correctly for non-concurrent tests using QuickSpec — the async variants and AsyncSpec exist separately for concurrent test code. The deprecation warnings produce noise across large codebases that still rely on the synchronous API with no immediate migration path. See: Quick#1199 (comment)
This file contains hidden or 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
1 participant
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.
PR Quick#1199 added @available(*, deprecated) annotations to all synchronous polling functions. These functions continue to work correctly for non-concurrent tests using QuickSpec — the async variants and AsyncSpec exist separately for concurrent test code.
The deprecation warnings produce noise across large codebases that still rely on the synchronous API with no immediate migration path.
See: Quick#1199 (comment)