Skip to content

Conversation

slavapestov
Copy link
Contributor

@slavapestov slavapestov commented Sep 27, 2018

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.

@slavapestov
Copy link
Contributor Author

@swift-ci Please test

@slavapestov
Copy link
Contributor Author

@swift-ci Please test source compatibility

@swift-ci
Copy link
Contributor

Build failed
Swift Test Linux Platform
Git Sha - a05c3de5476f08690cefe445fcde04c562830519

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - a05c3de5476f08690cefe445fcde04c562830519

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.
@slavapestov
Copy link
Contributor Author

@swift-ci Please test

@swift-ci
Copy link
Contributor

Build failed
Swift Test Linux Platform
Git Sha - a05c3de5476f08690cefe445fcde04c562830519

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - a05c3de5476f08690cefe445fcde04c562830519

@slavapestov
Copy link
Contributor Author

@DougGregor Mind taking a look? This is just a grab-bag of random unrelated changes at this point.

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.

2 participants