Skip to content

SILGen: Relax assertion about missing vtable entries in a class #29726

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

Conversation

slavapestov
Copy link
Contributor

Since resilient class metadata is built at runtime, we don't actually
care if there are missing vtable entries. The restriction was relaxed
in Sema in 9117c57, but SILGen still
had an assertion here.

Add a test and relax the assertion.

Fixes rdar://problem/58644615.

@slavapestov slavapestov requested a review from jckarter February 9, 2020 05:42
@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test

Since resilient class metadata is built at runtime, we don't actually
care if there are missing vtable entries. The restriction was relaxed
in Sema in 9117c57, but SILGen still
had an assertion here.

Add a test and relax the assertion.

Fixes <rdar://problem/58644615>.
@slavapestov slavapestov force-pushed the fix-silgen-vtable-assertion branch from 5ef6e6b to fc810e1 Compare February 11, 2020 00:28
@slavapestov
Copy link
Contributor Author

@swift-ci Please smoke test

@slavapestov slavapestov merged commit 988e9d6 into swiftlang:master Feb 11, 2020
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