Skip to content

Conversation

@jrose-apple
Copy link
Contributor

  • Explanation: Swift's access control restricts which decls can be used to match protocol requirements. This logic hadn't been updated for SE-0025, resulting in incorrect and confusing diagnostics.
  • Scope: Affects all access checking for protocol witnesses.
  • Issue: rdar://problem/27663492
  • Reviewed by: @slavapestov
  • Risk: Medium.
  • Testing: Added compiler regression tests, checked existing tests in this area.

...rather than relying on the access-as-spelled, which may be greater
than the effective access due to parent scopes.

(Some of this will get cleaned up with SR-2209.)

rdar://problem/27663492
(cherry picked from commit f65ad81)
@jrose-apple
Copy link
Contributor Author

@swift-ci Please test

@jrose-apple jrose-apple merged commit b74ae30 into swiftlang:swift-3.0-branch Aug 31, 2016
@jrose-apple jrose-apple deleted the swift-3-check-conformance-using-access-scopes branch August 31, 2016 00:26
kateinoigakukun added a commit that referenced this pull request Aug 31, 2022
[pull] swiftwasm from main
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant