Skip to content

Allow inheritance from resilient classes with missing members #24881

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 19, 2019

Conversation

beccadax
Copy link
Contributor

When a class has missing vtable entries, we don’t allow it to be subclassed. This is unnecessarily restrictive for resilient classes, and @_implementationOnly imports now make missing vtable entries much more common. This PR carves out an exception to that rule for resilient classes.

Fixes rdar://problem/50902125.

When a class has missing vtable entries, we don’t allow it to be subclassed. This is unnecessarily restrictive for resilient classes, and @_implementationOnly imports now make missing vtable entries much more common. This commit carves out an exception to that rule for resilient classes.

Fixes <rdar://problem/50902125>.
@beccadax
Copy link
Contributor Author

@swift-ci please smoke test

@slavapestov
Copy link
Contributor

Ah, nice catch.

@beccadax beccadax merged commit 91146d5 into swiftlang:master May 19, 2019
beccadax added a commit to beccadax/swift that referenced this pull request May 20, 2019
…den-method

Allow inheritance from resilient classes with missing members
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.

3 participants