Suggest narrowing an existing availability context, when feasible. #6924
Conversation
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
jrose-apple
approved these changes
Jan 20, 2017
|
@swift-ci please smoke test and merge |
|
Nitpick: typo in PR title, "exising" |
graydon
changed the title
|
@swift-ci please smoke test and merge |
1 similar comment
|
@swift-ci please smoke test and merge |
graydon
deleted the
rdar-28815071-fixit-to-narrow-availability-check
branch
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.
Targeted fix for the case of a user having an existing type refinement context
(via #available or @available guard) that doesn't restrict to the version range
required by the callee: provides a specific fixit to adjust the existing guard to
match requirement, rather than suggesting introducing a new one.
rdar://problem/28815071