Skip to content

IRGen type lowering cleanup #19723

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

While working on the YAML type info deserialization logic I cleaned up some code in this area.

A few utility methods would bypass computing the TypeInfo for a tuple,
but they were only used in assertions or used in places where I can't
imagine tuples coming up often enough for it to matter.
This was an old workaround for a bug that should no longer
happen now that convenience initializers only have allocating
entry points.
@slavapestov
Copy link
Contributor Author

@swift-ci Please test

@slavapestov
Copy link
Contributor Author

@swift-ci Please test source compatibility

@slavapestov slavapestov requested a review from rjmccall October 5, 2018 00:02
@rjmccall
Copy link
Contributor

rjmccall commented Oct 5, 2018

I think the idea with the forward-declarations was to make sure that self-references got a nice type during lowering. But I don't really know why that would be important anymore, honestly, since none of our valid recursion cases needs that type — e.g. we don't have well-typed pointers at the SIL level.

@slavapestov slavapestov merged commit 4ba96f2 into swiftlang:master Oct 5, 2018
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