Skip to content

Teach Named Lazy Member Loading To Import Inherited Constructors #28840

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 4 commits into from
Dec 19, 2019

Conversation

CodaFi
Copy link
Contributor

@CodaFi CodaFi commented Dec 18, 2019

Flush a longstanding hack in name lookup by teaching the Clang Importer to import inherited constructors during lazy member loading.

This effectively shepherds one half of #26975.

@CodaFi CodaFi requested a review from slavapestov December 18, 2019 00:35
@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 18, 2019

@swift-ci please test

@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 18, 2019

@swift-ci please test source compatibility

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - 793e7df99ea13253e41e7992cfdd8aca206f9226

@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 18, 2019

@swift-ci please smoke test

@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 18, 2019

@swift-ci please smoke test

@CodaFi CodaFi mentioned this pull request Dec 18, 2019
@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 18, 2019

Infrastructure failure

@swift-ci please smoke test

The DWARF Importer does not yet know how to answer a request at the level of a single member.  All the tests that saw this as an observable behavior were actually seeing a complete cache fill from lazy member loading an initializer fail over to flushing the member table and rebuilding it by forcing all the members. Given that the cache flush is something we're trying to avoid in general, this is obviously undesirable behavior.

Now that we're no longer flushing the cache for initializers, the DWARF Importer needs to simulate the old behavior and completely deserialize members of loaded types.  This pessimization is justified anyways, considering if you're loading from DWARF, you're probably about to print the type and its fields anyways.
@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 19, 2019

@swift-ci please smoke test and merge

1 similar comment
@CodaFi
Copy link
Contributor Author

CodaFi commented Dec 19, 2019

@swift-ci please smoke test and merge

@swift-ci swift-ci merged commit 9209e4f into swiftlang:master Dec 19, 2019
@CodaFi CodaFi deleted the constrnation branch December 19, 2019 02:13
@slavapestov
Copy link
Contributor

Thanks!

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