-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Preliminary cleanups for creating fewer GenericSignatureBuilders #19580
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
Conversation
Canonicalizing GenericFunctionTypes is a very expensive operation, and we assert elsewhere that they do not contain archetypes.
…ureBuilder::inferRequirements()
@swift-ci Please test |
@swift-ci Please test source compatibility |
Build failed |
Build failed |
This was mechanically converted from the old function type representation, but the 'single tuple argument' case is bogus.
Most of the time we don't need it, and accessing a generic environment on a deserialized declaration creates a GenericSignatureBuilder.
…berNamesTableInfo Named lazy member loading skips constructors right now anyway for other reasons, but trying to re-enable it hits this problem first.
a05c3de
to
87a49ff
Compare
@swift-ci Please test |
Build failed |
Build failed |
@DougGregor Mind taking a look? This is just a grab-bag of random unrelated changes at this point. |
I'm working on some experimental changes which reduce the number of GenericSignatureBuilders that get created. This PR has a bunch of smaller changes that fell out of this work.